Bug#567468: (boot time consequences of) Linux mdadm superblock question.
On Mon, 2010-02-22 at 08:04 +1300, Daniel Reurich wrote:
> On Sun, 2010-02-21 at 18:14 +0100, martin f krafft wrote:
> > also sprach Daniel Reurich <daniel@centurion.net.nz> [2010.02.19.0351 +0100]:
> > > But if a generated 'system uuid' value (I just suggested the root fs
> > > UUID because it would be highly unlikely to be unchanged, and nobody
> > > would be likely to fiddle with it) was copied into a file
> > > called /etc/system_uuid and copied into the initrd, then we could add
> > > put into mdadms hook script in initramfs-tools, to verify and update the
> > > homehost variable in the boot time required raid volumes when ever a new
> > > initrd is installed. (This generally happens on debian whenever a
> > > kernel is installed and mdadm is installed or upgraded.
> >
> > Neil's point is that no such value exists. The root filesystem UUID
> > is not available when the array is created. And updating the
> > homehost in the RAID metadata at boot time would defeat the purpose
> > of homehost in the first place.
>
> I said copy
> >
I meant to say: I said copy it into a file that get's stored in the
initrd image which can be used for the homehost in mdadm auto-detection
of root raid.
Reply to: