Description of problem: [root@dell-p390n-01 ~]# service kdump restart Stopping kdump:[ OK ] Detected change(s) the following file(s): /etc/kdump.conf Rebuilding /boot/initrd-2.6.18-274.el5kdump.img Warning! Lack of dump target specification means default option is ignored! Starting kdump:[ OK ] [root@dell-p390n-01 ~]# echo c > /proc/sysrq-trigger SysRq : Trigger a crashdump Memory for crash kernel (0x0 to 0x0) notwithin permissible range Warning: pci_mmcfg_init marking 256MB space uncacheable. ounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Loading scsi_mod.ko module Loading sd_mod.ko module Loading libata.ko module Loading ata_piix.ko module Loading ahci.ko module Loading jbd.ko module Loading ext3.ko module Loading dm-mod.ko module Loading dm-log.ko module Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Waiting for required block device discovery Waiting for sda...Found Creating Block Devices Creating block device ram0 Creating block device ram1 Creating block device ram10 Creating block device ram11 Creating block device ram12 Creating block device ram13 Creating block device ram14 Creating block device ram15 Creating block device ram2 Creating block device ram3 Creating block device ram4 Creating block device ram5 Creating block device ram6 Creating block device ram7 Creating block device ram8 Creating block device ram9 Creating block device sda Making device-mapper control node Scanning logical volumes Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2 Activating logical volumes 2 logical volume(s) in volume group "VolGroup00" now active Attempting to enter user-space to capture vmcore Creating root device. Checking root filesystem. fsck 1.38 (30-Jun-2005) fsck: WARNING: couldn't open /etc/fstab: No such file or directory e2fsck 1.38 (30-Jun-2005) fsck.ext3: while determining whether /dev/VolGroup00/LogVol00 is mounted. /dev/VolGroup00/LogVol00: recovering journal /dev/VolGroup00/LogVol00: clean, 124442/96632832 files, 3794983/96624640 blocks Mounting root filesystem. Trying mount -t ext4 /dev/VolGroup00/LogVol00 /sysroot Trying mount -t ext3 /dev/VolGroup00/LogVol00 /sysroot Using ext3 on root filesystem Switching to new root and running init. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Configure kdump on RHEL5 2. Configure kdump.conf to dump to local filesystem 3. Trigger a crash
Created attachment 529744 [details] Proposed patch
Tested with latest build on dell-p390n-01.lab.bos.redhat.com: ======================================================================= [root@dell-p390n-01 ~]# grep -v ^# /etc/kdump.conf ext3 /dev/mapper/VolGroup00-LogVol00 core_collector makedumpfile -E -d 31 default shell [root@dell-p390n-01 ~]# rpm -q kexec-tools kexec-tools-1.102pre-142.el5 [root@dell-p390n-01 ~]# hostname dell-p390n-01.lab.bos.redhat.com [root@dell-p390n-01 ~]# service kdump start Detected change(s) the following file(s): /etc/kdump.conf Rebuilding /boot/initrd-2.6.18-274.el5kdump.img Starting kdump:[确定] [root@dell-p390n-01 ~]# echo c > /proc/sysrq-trigger --------------------------------------------------------- SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB) sda: Write Protect is off SCSI device sda: drive cache: write back sda: sda1 sda2 Making device-mapper control node Scanning logical volumes Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2 Activating logical volumes 2 logical volume(s) in volume group "VolGroup00" now active Saving to the local filesystem /dev/mapper/VolGroup00-LogVol00 e2fsck 1.38 (30-Jun-2005) /dev/mapper/VolGroup00-LogVol00: recovering journal /dev/mapper/VolGroup00-LogVol00: clean, 87103/96632832 files, 3678594/96624640 blocks kjournald starting. Commit interval 5 seconds EXT3 FS on dm-0, internal journal EXT3-fs: mounted filesystem with ordered data mode. [100 %] The dumpfile is saved to /mnt//var/crash/127.0.0.1-2011-12-02-03:05:47/vmcore-incomplete. makedumpfile Completed. Saving core complete md: stopping all md devices. Synchronizing SCSI cache for disk sda: Restarting system. Move to VERIFIED.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No description necessary
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-0152.html