From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Brown Subject: Re: (boot time consequences of) Linux mdadm superblock question. Date: Thu, 18 Feb 2010 16:10:12 +1100 Message-ID: <20100218161012.704b43a6@notabene.brown> References: <201002140251.59668.volkerarmin@googlemail.com> <20100217181016.GA14983@emergent.ellipticsemi.com> <201002171927.07051.volkerarmin@googlemail.com> <20100217183703.GA15446@emergent.ellipticsemi.com> <20100218102407.49f73d67@notabene.brown> <20100218025809.GA20358@khazad-dum.debian.net> <20100218032610.GB1991@lapse.rw.madduck.net> <1266465801.11568.183.camel@localhost.localdomain> <20100218044004.GC5136@lapse.rw.madduck.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100218044004.GC5136@lapse.rw.madduck.net> Sender: linux-raid-owner@vger.kernel.org To: martin f krafft Cc: Daniel Reurich , linux-raid List-Id: linux-raid.ids On Thu, 18 Feb 2010 17:40:04 +1300 martin f krafft wrote: > also sprach Daniel Reurich [2010.02.18.1703 +1300]: > > > Debian experimental. But so far, I was unable to get rid of > > > mdadm.conf because it only works without the info in that file if > > > the homehost is correctly encoded in the metadata. So the challenge > > > I am facing is http://bugs.debian.org/567468. > > > > Why not use an installation generated uuid like that of the root > > filesystem for the homehost identifier. It's less likely to change then > > just about any other system identifier. > > This is a great idea. While I would still have to store that UUID in > the initrd, as you say, it's 99% likely to remain constant, and when > it changes, it's 99% likely that the admin is doing something that > will require more work, so we can resort to 100% hoping that s/he > knows what she's doing. > > Neil? > Sure, you can do that. 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 NeilBrown