The code is supposed to auto-detect changes, but there are still (mostly obscure) ways that confuse it. The safest approach if you want to remove the vgscan at boot is to specify the precise VGs you want to activate by name on the vgchange command line instead of letting it default to 'all'. So 'vgchange -ay root_vg home_vg' etc. instead of 'vgchange -ay'. Then it knows what VGs are supposed to be there, and if it didn't think it needed to scan but doesn't see one or more of them that'll be enough to trigger the scan. Alasdair _______________________________________________ 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/
