David Teigland dd6a202831 lvchange: deactivate is always possible in foreign vgs ... The only realistic way for a host to have active LVs in a foreign VG is if the host's system_id (or system_id_source) is changed while LVs are active. In this case, the active LVs produce an warning, and access to the VG is implicitly allowed (without requiring --foreign.) This allows the active LVs to be deactivated. In this case, rescanning PVs for the VG offers no benefit. It is not possible that rescanning would reveal an LV that is active but wasn't previously in the VG metadata.		2015-02-25 14:58:49 -06:00
..
toolcontext.c	toolcontext: Fix lvmlocal.conf load fail path.	2015-02-25 16:36:47 +00:00
toolcontext.h	lvchange: deactivate is always possible in foreign vgs	2015-02-25 14:58:49 -06:00