David Teigland e710bac03d Revert "lvmcache: skip drop when vg_write lock is not held" ... This reverts e28e22b9e1 The problem that that commit was fixing (pytest failure) no longer appears with the current code, so the commit is not needed. That commit is a problem for pvchange, because it prevents lvmcache from retaining VG metadata even while the global lock is held. pvchange holds the global lock to ensure that VG metadata is kept in lvmcache throughout processing. If the cache is not kept, a PV with zero MDAs will appear first in its actual VG and then appear again in the orphan VG. It wrongly appears a second time in the orphan VG only if the actual VG is dropped from lvmcache.		2016-01-14 13:34:36 -06:00
..
lvmcache.c	Revert "lvmcache: skip drop when vg_write lock is not held"	2016-01-14 13:34:36 -06:00
lvmcache.h	vgrename: use process_each_vg	2015-12-14 14:26:47 -06:00
lvmetad.c	lvmcache: new function to check if VG is foreign	2015-11-30 11:54:56 -06:00
lvmetad.h	lvmcache: new function to check if VG is foreign	2015-11-30 11:54:56 -06:00