On Thu, 2005-01-13 at 13:59 +0100, Guido Guenther wrote: > On Wed, Jan 12, 2005 at 11:02:50PM +0100, Erik van Konijnenburg wrote: > > The cause: multipath adds a script /etc/mkinitrd/scripts/01_udev; this > > mounts a new /dev and lets udevstart run on it. This happens after > > /script is executed, which is where the LVM command "vgchange -a y vg0" > > is executed to create LVM devices. Unfortunately, udevstart has no way > > of creating the /dev/mapper nodes required by LVM, so the root device > > /dev/mapper/vg0 stays missing. > Uargh, that is very bad. We should run the multipath stuff before the > LVM stuff anyway since you most likely want LVM over the multipath (if > not you're of corse still free to do so). I'll have to have a look at > the scripts of 0.4.2 to see if we can do this easily. Until then it > would probably be best to pull the initrd related parts from > multipath-tools again since they seem to cause quiet some trouble at the > moment and are "only" needed if your root device is multipathed. > Cheers, > -- Guido > > The multipath tools mkinitrd scripts shouldn't have to cope with udev in the first place. I did it as a proof of concept, but in the long run the debian udev packager should make a push into initrd. When we get there the multipath stuff will layer properly. In the mean time, I agree the script shouldn't be installed by default, or we can make it depend on a variable set in mkinitrd.conf.
regards, -- christophe varoqui <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
