Red Hat Bugzilla – Bug 479211
[PATCH] mkdumprd does not work for raid-rooted installations
Last modified: 2010-10-23 02:49:45 EDT
Created attachment 328425 [details]
A patch that fixes mkdumprd with raid
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. ARRAY /dev/md0 level=raid5 ... in /etc/mdadm.conf
2. /sbin/mkdumprd -v -d -f /boot/initrd-2.6.18-116.el5kdump.img 2.6.18-116.el5
Module raid5 can not be found
Initrd built with module raid456.ko included
I think this is a duplicate of bz 472915. please try the patch there and let me know thanks.
Created attachment 328595 [details]
A patch that fixes mkdumprd with raid (merged with fix for #472915)
(In reply to comment #1)
> I think this is a duplicate of bz 472915. please try the patch there and let
> me know thanks.
It doesn't seem like such. A side effect of my patch would be that it would also fix the bug #472915 problem (since sed -n .../p construct is used which makes the matching of ARRAY lines more robust) though. I merged the two patches, attaching the result.
*** Bug 472915 has been marked as a duplicate of this bug. ***
fixed in 1.102pre-59.el5. Thanks!
I'm wondering if this is to be fixed in Fedora as well? Looking at the Fedora mkdumprd it seems to have the same problem, I'm unable to verify that though, since I don't have a raid installation.
~~ Attention - RHEL 5.4 Beta Released! ~~
RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner!
If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity.
Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value.
Questions can be posted to this bug or your customer or partner representative.
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.