Comment 2 for bug 252345
Revision history for this message
| ceg (ceg) wrote Re: mdadm.conf is crated with explicit ARRAY statements prevents hotplug autodetection | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Well, the issue filed here, is
autocreated mdadm.conf prevents autodetection of cold- and hotplugging.
I found out not only the ARRAY lines, but also the homehost prevents autotection of arrays.
The homehost feature may have been good to prevent systems with global "mdadm --assemble --scan" booting from unsyncing partly pluged in arrays and device name switchtichg in the old days.
With UUID checking in mdadm, udev and dynamic device names working, we need a way to unset the homehost, to set it to "any" or some other way so "mdadm --incremental /dev/%k" will really setup all completed arrays that are attatched when it is called from udev rules.
Something like: HOMEHOST "" in mdadm.conf or --homehost=any on the comandline.