Re: (boot time consequences of) Linux mdadm superblock question.

[Neil Brown <neilb@suse.de>]

On Thu, 18 Feb 2010 18:21:45 +1300
martin f krafft <madduck@madduck.net> wrote:

> also sprach Neil Brown <neilb@suse.de> [2010.02.18.1810 +1300]:
> > You would put it in /etc/mdadm.conf
> > The format would be something like:
> > 
> >   ARRAY /dev/md/root uuid=xxxx:xxxx:xxxx:xxxx
> > 
> > and any array found with that uuid would be assembled as /dev/md/root
> 
> No, we mean using the UUID of the root filesystem (vol_id, not
> mdadm's UUID) as the homehost identifier, instead of the hostname.
> 

You can set homehost to anything you like, in mdadm.conf or on the command
line..

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)...

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.

So I don't think I know what is really being proposed.

??

NeilBrown