mdadm: different component-count in superblocks prevents assembly

[Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>]

Hello Again :)

Having a component device with slightly different superblock
characteristics in the system prevents mdadm from assembling arrays.
For example:
	mdadm --fail /dev/mdx /dev/xdx
	mdadm -G -n y-1 /dev/mdx
would lead to a non-assemble-able /dev/mdx as long as /dev/xdx remains
in the system and thus probably leads to an unbootable system should
/dev/mdx be /.

Wouldn't it make sense to weight other superblock parameters like the
event counter a little higher, i.e. under all unique-id'ed devices
consider first only those with the highest equal event count and only
afterwards compare the rest of the superblocks (and then fail, if they
don't match, of course)?


regards
   Mario
-- 
Goethe war nicht gerne Minister. Er beschaeftigte sich lieber geistig.
                                            -- Lukasburger Stilblueten