RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1282699 - vmcore cannot be generated if noauto is set for dump target which is local disk
Summary: vmcore cannot be generated if noauto is set for dump target which is local disk
Keywords:
Status: CLOSED DUPLICATE of bug 1186708
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kexec-tools
Version: 7.1
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: kdump team
QA Contact: Kernel General QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-17 07:24 UTC by shiwang
Modified: 2019-08-15 05:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-17 08:20:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description shiwang 2015-11-17 07:24:25 UTC 
Description of problem:

Vmcore cannot be generated if noauto is set for dump target which is local disk.
The customer don't want to mount kdump dump target at boot. So he need to use
noauto option for the dump target device. But after using it, vmcore cannot be
generated.

Version-Release number of selected component (if applicable):

kexec-tools-2.0.7-19.el7.x86_64
kernel 3.10.0-229.7.2.el7.x86_64

How reproducible:

Steps to Reproduce:

1. add an additional disk (/dev/sdb)

2. set the disk as dump target

#cat /etc/kdump.conf
xfs UUID="0603cfba-c0c6-4bf2-8ed0-a0cae32aeafe"
path /var/crash
core_collector makedumpfile -l --message-level 1 -d 31

#blkid
/dev/sdb: UUID="0603cfba-c0c6-4bf2-8ed0-a0cae32aeafe" TYPE="xfs" 

3. set the disk into /etc/fstab

#cat /etc/fstab
UUID=0603cfba-c0c6-4bf2-8ed0-a0cae32aeafe /dump     xfs defaults,noauto 0 0

4. mount the /dev/sdb in order to create initrd for kdump.

#mount /dev/sdb

5. recreate the kdump initrd file.

#kdumpctl restart

6. umount the /dev/sdb

#umount /dev/sdb

7. Trigger the kernel panic

#echo c > /proc/sysrq-trigger

8. After reboot, mount the /dev/sdb and check the result.

Actual results:

No vmcore files.

Expected results:

vmcore and vmcore-dmesg.txt files exist.

Additional info:

I tested it with same procedure as above using RHEL7.0 and it works fine.

kexec-tools-2.0.4-32.el7.x86_64
kernel　3.10.0-123.el7.x86_64

My question is, do we need to mount kdump dump target at boot time in order 
to generate vmcore? Is it a change recently?

Best regards
Shiyu Wang
Technical Support Engineer
Comment 2 Minfei Huang 2015-11-17 07:43:47 UTC 
Hi.

This bug is fixed in version 2.0.7-26. Maybe you can try kexec-tool version 2.0.7-26 or later.

Thanks
Minfei
Comment 4 shiwang 2015-11-17 08:20:05 UTC 
Hi All,

Thank you very much! It works in 2.0.7-26. I will close this BUG.

BR,
Shiwang

*** This bug has been marked as a duplicate of bug 1186708 ***
Note You need to log in before you can comment on or make changes to this bug.