Bug 719490

Description of problem:
mkdumprd fails to build dump image when run, the error reported seems to indicate a problem parsing the mdadm.conf file.

My file has been manually regenerated using mdadm --detail --scan < /etc/mdadm.conf and so doesnt have some of the options generated by a "normal" generation, but is however perfectly suitable for use.

I have had a look at the source code (at http://webcache.googleusercontent.com/search?q=cache:lIbQkzFEzyEJ:web.mit.edu/~mkgray/afs/bar/sbin/mkdumprd+no+module+array+found+mkdumprd+rhel6&cd=9&hl=en&ct=clnk&gl=au&source=www.google.com.au) and it is using the following to generate the array lists:

for i in `cat /etc/mdadm.conf | grep "^[:space:]*[^#]" | grep ARRAY | sed -e's/\(^.*level=\)\(.*$\)/\2/' | cut -d" " -f1`;

My file has the following:
ARRAY /dev/md0 metadata=1.0 name=localhost.localdomain:0 UUID=7f38c153:a4bbcb06:92d4cf29:8892058f
ARRAY /dev/md1 metadata=1.2 name=anubis.homedomain:3 UUID=cf37f2b4:1c166f53:3acd9528:1409ded8
ARRAY /dev/md2 metadata=1.2 name=1 UUID=6d4009b9:1162c065:969b26ba:adc2dc02

(FYI, ignore the names, some were generated by anaconda, some after install)

As you can see, mine does not have the level in it, and seems to break it.

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


How reproducible: Everytime


Steps to Reproduce:
1. switch to root
2. attempt to start kdump (using service kdump start)
3. kdump attempts to create dump img, fails
  
Actual results:
fails with error:
No kdump initial ramdisk found.                            [WARNING]
Rebuilding /boot/initrd-2.6.32-131.4.1.el6.x86_64kdump.img
No module ARRAY found for kernel 2.6.32-131.4.1.el6.x86_64, aborting.
Failed to run mkdumprd

Expected results:
success in creating dump img, kdump starting successfully.

Additional info:
Again to repeat the above, i dont have a "system generated" mdadm.conf, and it does not show the levels. If this not a bug, please advise, it seems a bit strange however that it would work for the OS, but not for an app that depends on it. If you can advise another way to create the mdadm.conf that you would like me to test, please let me know.

Also, there were previous bugs sent in about this back in RHEL5 / FC13, and they had system generated mdadm.conf files that also did not contain the level.

One of those can be found at: https://bugzilla.redhat.com/show_bug.cgi?id=629013

As i dont have a system generated /etc/mdadm.conf that contains the level portion im unable to replicate a file that matches the layout expected. If you can advise how it should look i could replicate for testing.