Comment 37 for bug 136252
Revision history for this message
| ceg (ceg) wrote Re: [karmic] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays. | #37 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Adopting from #226484 (now a duplicate of this one):
This is a bug with mdadm --incremental not doing hotplug, because it looks for permission to do so in mdadm.conf.
On hotplug systems mdadm.conf should not have to contain any specific references, to make things clear and for backwards compatibility maybe it could contain explicit "any" statements like this:?
DEVICE <any>
HOMEHOST <any>
ARRAY <any>
This whole bussiness of locking down array assembly (homehost,ARRAY) may just be due to the historical (suboptimal) mdadm design to assamble raids going by major/minor numbers saved in the superblocks. Those should always be considered being dynamic (depreciated as a reference). Using --assemble --uuid mdadm takes a UUID and matches this unique but same UUID to determine member devices, this is appropriate for default behavour.
Of course we should refrain from running arrays that are not complete (to avoid leading them to desync by subsequent writes), unless it is required to recover data or boot from a specific failed array. For this case we should use --run <specific device> manually or in a startup scripts.