-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 30 Oct 2005 19:06:09 -0500 Daniel Jacobowitz <[EMAIL PROTECTED]> wrote:
> On Mon, Oct 31, 2005 at 12:37:49AM +0100, Jonas Smedegaard wrote: > > In your case it would make sense to only have the image tied to the > > UUID, but in other cases perhaps it would make sense to ignore UUID > > and instead only use device names. > > Even SCSI ID would be an improvement! This is exposed via sysfs, > though not wonderfully. Use the device path followed by block/. But > that has plenty of failure modes too. Yaird does discovery at ramdisk build time, but (to keep image minimal) not at boot time. And mdadm cannot be passed a SCSI ID, so I believe storing only SCSI ID with the image wouldn't work (without major changes to yaird). > > What I believe will work (I haven't tried myself) is to > > edit /etc/yaird/Templates.cfg and at TEMPLATE mdadm remove the third > > line of the script (remember to also remove the trailing "\" in the > > line above). > > The device nodes wouldn't be right. The original failure was trying > to create /dev/sdb2, when there no longer was such a device (it only > had one partition). My suggestion here is to _strip_ device nodes, leaving only UUID. It should help in your scenario (same disks, device numbers moving around) but will not work for other scenarios. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDZkmUn7DbMsAkQLgRAn8bAKCG8gkVM7mqF6hBHth7lWfbXvOPiwCgnwq7 cDEDVB5SDe/Xuvch2HDieaw= =ju9p -----END PGP SIGNATURE-----
