On Thu, 18 Feb 2010 17:40:04 +1300 martin f krafft <madduck@xxxxxxxxxxx> wrote: > also sprach Daniel Reurich <daniel@xxxxxxxxxxxxxxxx> [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 -- 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
