On Tue, Feb 16, 2010 at 03:37:08PM +0100, Volker Armin Hemmann wrote:
so assume you have an initrd and metadata 1.x without auto assembling.
You do some changes to the raid and screw up something else. Next boot nothing
works. Mostly because the mdadm.conf in your initrd is not correct.
You whip out your trusty usb stick with a resuce system - and you are stuck.
If autoassembling would work, you would have working md devices you could
mount and edit the files you have to. But you don't and the mdadm.conf in the
initrd is outdated.
Sounds like 'you are screwed'.
did you ever try this?
mdadm is able to activate an array without need of any configuration
file.
The reason a configuration file is copied in initrd is solely to
preserve non-default activation parameters (i.e. array name) and such.
And that because ...? Is there any good reason not to have autoassmbling in
the kernel?
about the same reason why the X server is not in the kernel as well.
L.
--
Luca Berra -- bluca@xxxxxxxxxx
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
