Bug 630598
| Summary: | bad handling of mdadm.conf in mkdumprd | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jeff Layton <jlayton> | ||||
| Component: | kexec-tools | Assignee: | Neil Horman <nhorman> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 14 | CC: | anton, nhorman, qcai, steved | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | kexec-tools-2.0.0-39.fc14 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-09-16 03:50:56 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Created attachment 447535 [details]
patch to not find modules for mdadm
I just realized that since we pull in all running modules now, we need to need to explicitly find the software raid modules. Please confirm that this patch solves your issue. Thanks!
Thanks Neil. Yep, that seemed to fix it. kexec-tools-2.0.0-39.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/kexec-tools-2.0.0-39.fc14 kexec-tools-2.0.0-39.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |
mkdumprd does this: if [ -f /etc/mdadm.conf ] then cp /etc/mdadm.conf $MNTIMAGE/etc bin="$bin /sbin/mdadm" for i in `cat /etc/mdadm.conf | grep ARRAY | sed -e's/\(^.*level=\)\(.*$\)/\2/' | cut -d" " -f1` do findmodule $i done fi My mdadm.conf has this: ARRAY /dev/md1 uuid=aebf2661:f2abc19d:9b68e17f:deb7fa33 ARRAY /dev/md5 uuid=65b98409:d47e87e6:45d32a1c:5f22a85e When I run the stuff in backticks against it, I get this output: $ cat /etc/mdadm.conf | grep ARRAY | sed -e's/\(^.*level=\)\(.*$\)/\2/' | cut -d" " -f1 ARRAY ARRAY ...the findmodule command then fails to find any module called ARRAY (obviously).