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

[Daniel Reurich <daniel@centurion.net.nz>]

On Thu, 2010-02-18 at 17:40 +1300, martin f krafft wrote:
> also sprach Daniel Reurich <daniel@centurion.net.nz> [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.

It'd already be there if they used it in /etc/fstab.  (I wish they would
as it would solve a whole lot of other media portability problems as
well, but that's another issue.)

-- 
Daniel Reurich.

Centurion Computer Technology (2005) Ltd
Mobile 021 797 722