* mdadm: different component-count in superblocks prevents assembly
@ 2007-09-03 20:42 Mario 'BitKoenig' Holbe
0 siblings, 0 replies; only message in thread
From: Mario 'BitKoenig' Holbe @ 2007-09-03 20:42 UTC (permalink / raw)
To: linux-raid
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2007-09-03 20:42 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-09-03 20:42 mdadm: different component-count in superblocks prevents assembly Mario 'BitKoenig' Holbe
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).