On Wed, 2022-03-09 at 11:07 -0600, Roger Heflin wrote: > > I have also had luck with making sure multipath is in the initramfs, > and adding rd.lvm.vg=<rootvgnameneededforboot> on the kernel boot > line > so that in the initramfs only the VG needed for boot up is started up > early inside the initramfs. That has typically let multipathd > inside the initrd grab any other devices and configure them for > multipath before LVM activates them. > Agreed, tricks like this are often helpful. My goal is (and has to be, as the maintainer of the multipath package on a distro) to make this work out of the box, without any configuration effort on the part of the user, in arbitrary environments and storage setups. If this stuff fails, users end up in emergency mode, and with no clue how to recover. Recent changes in multipath-tools have modified multipathd startup to occur earlier in the boot sequence, which is a good thing in general, but tends to increase the visibilty of shortcomings in other layers of the storage stack. Regards, Martin _______________________________________________ linux-lvm mailing list linux-lvm@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
