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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
"when a woman marries again it is because she detested her first husband.
 when a man marries again it is because he adored his first wife.
 women try their luck; men risk theirs."
                                                        -- oscar wilde
 
spamtraps: madduck.bogus@xxxxxxxxxxx

Attachment: digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux