On Mon, Mar 04, 2013 at 06:26:32PM -0500, Daniel Dickinson wrote: > However, it seems that /dev/<vg> is not created for the nested volume > group by the /etc/init.d/lvm2 initscript, and the nested volume group is > not started on boot. > > A second vgscan / vgchange -ay starts it. The upstream uevent-driven activation upstream should address that:
New block dev -> uevent -> pvscan the new device -> activation of LV containing PV -> new LV block dev containing that PV -> uevent ->pvscan new PV -> ... (see lvchange -aay and activation/auto_activation_volume_list in lvm.conf) Alasdair -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org