> Attached is a question I've asked my xen hosting provider's technical > support and the answer they've supplied. > > Sam sais "There is no LVM module available, so you would need to compile > LVM by yourself from the Xen kernel sources." but I've no problem > loading dm_mod and to my understanding of LVM, this is the only module > needed. So is he just wrong? If you're able to activate the volumes after the system has booted (which the discussion below suggests), then the device-mapper modules would already be available so there's no need to compile anything. > The issue is that logical volumes are not activated on bootup. This prevents me from using /etc/fstab to mount them. > > root@shacharor:~# lvdisplay | grep 'LV Status' && udevtrigger && udevsettle && lvdisplay | grep 'LV Status' > LV Status NOT available > LV Status available > root@shacharor:~# > > This shows that udev handles logical volumes correctly and does activate them. But why doesn't it do it on bootup? If the volumes aren't created at boot time you're probably missing the relevant stuff in your initial ram disk... usually, if you're root fs is on an LVM volume, the ram disk would contain the relevant dm_* kernel modules and a script that (amongst other things) loads the relevant kernel modules and activates the volumes. Your simplest solution may be to just add "vgscan --mknodes" and "vgchange -ay" to rc.local (its uglier than fixing the initrd, but you may not be able to recreate the initrd in your situation). --Dave _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
