also sprach Neil Brown <neilb@suse.de> [2010.02.18.1834 +1300]:
> But it would be rather awkward to store the uuid of the root
> filesystem in the metadata for the array that stores the root
> filesystem (and so is created before the root filesystem)...
True. You'd have to update the superblock UUID right after creation
of the filesystem. That doesn't sound like a robust strategy to
making mdadm.conf optional.
> Are you suggesting that when mdadm finds some bits that looks like
> the form an array it should test-assemble it, look inside for
> a filesystem, extra the uuid of that filesystem and compare
> against some known uuid before deciding whether to assemble that
> array or not? I hope not.
Hehe, that would be fun, wouldn't it? ;)
> So I don't think I know what is really being proposed.
I really would like to make mdadm.conf optional and still have
things work incrementally from initrd.
--
martin | http://madduck.net/ | http://two.sentenc.es/
stupidity management for the superuser
is a user space issue in unix systems.
-- alan cox
spamtraps: madduck.bogus@madduck.net
Attachment:
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)