Red Hat Bugzilla – Bug 458702
kdump initrd hangs waiting on cciss or md devices
Last modified: 2009-01-20 15:59:38 EST
Created attachment 313983 [details]
patch to exclude md and cciss from critical_disks
Description of problem:
The recent changes to kdump mkdumprd to wait until the needed devices are in place before mounting the root filesystem hangs on md or cciss devices. This is due to how it parses the devices to be able to find them in sysfs.
Since these devices are always there once the driver is loaded we don't have the race condition issue so the easiest is to just exclude them from etc/critical_disks.
I am attaching a patch to mkdumprd that does that. Patch has been tested on systems with "md" and "cciss" disks.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Created attachment 313995 [details]
updated patch to properly handle raid cases
In the process of looking at this we also found that for raid devices it does not add the /dev/sd* devices needed to critical_disks as it should. This is an updated patch that has the fix mentioned in the orignal comment and also fixes this raid case.
This has been tested on 3 different ia64 systems with these configs:
lvm on top of raid on scsi disks
raid on scsi disks
lvm on top of cciss disks
all appear to kdump properly and inspection of etc/critical_disks shows what is expected (the needed sd disks only).
fixed in -32.el5. Thanks!
Thanks, I have verified that -32.el5 does indeed work nicely.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.