David Teigland 899a4ca275 lvmlockd: fix dropping PVs in rescanning VG ... This fixes a problem in commit ae0a8740c. The problem in that commit was that all existing PVs are initially dropped from lvmetad. This works if the VG is updated at the end, which replaces the dropped PVs, but if the rescan finds that the VG seqno is unchanged, it leaves the cached VG in place. So, we should only drop the existing PVs in lvmetad when the VG is going to be updated.		2016-06-17 12:21:09 -05:00
..
lvmcache.c	vgcreate, pvcreate, vgextend: don't use a device with duplicates	2016-06-07 15:21:07 -05:00
lvmcache.h	vgcreate, pvcreate, vgextend: don't use a device with duplicates	2016-06-07 15:21:07 -05:00
lvmetad.c	lvmlockd: fix dropping PVs in rescanning VG	2016-06-17 12:21:09 -05:00
lvmetad.h	pvscan: use process_each_vg for autoactivate	2016-05-23 11:57:32 -05:00