udev not using mdadm incremental
Bug #157981 reported by
Daniel Miller
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mdadm (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Problem occurs when activating an existing raid array on boot. My configuration, which exposed this, was four SATA drives in a Raid-10 configuration created with mdadm. On boot, udev appears to be entering some race conditions with mdadm - the array is activated with only three of the drives.
This appears to be an issue with using the "auto" detection of mdadm. Consulting the linux-raid mailing list shows the "incremental" flag was expressly created for udev - but it doesn't appear to have be being used by udev! Please contact the mdadm developers (like Neil Brown) to get this resolved.
Changed in mdadm (Ubuntu): | |
status: | Incomplete → Fix Released |
To post a comment you must log in.
Can you supply a reference to the mailing list post defining --incremental
I suspect this option has been added since our mdadm packages were frozen.