David Teigland 9b640c3684 pvscan: use process_each_vg for autoactivate ... This refactors the code for autoactivation. Previously, as each PV was found, it would be sent to lvmetad, and the VG would be autoactivated using a non-standard VG processing function (the "activation_handler") called via a function pointer from within the lvmetad notification path. Now, any scanning that the command needs to do (scanning only the named device args, or scanning all devices when there are no args), is done first, before any activation is attempted. During the scans, the VG names are saved. After scanning is complete, process_each_vg is used to do autoactivation of the saved VG names. This makes pvscan activation much more similar to activation done with vgchange or lvchange. The separate autoactivate phase also means that if lvmetad is disabled (either before or during the scan), the command can continue with the activation step by simply not using lvmetad and reverting to disk scanning to do the activation.		2016-05-23 11:57:32 -05:00
..
lvmcache.c	pvremove: allow clearing a duplicate PV	2016-05-16 14:40:43 -05:00
lvmcache.h	pvremove: allow clearing a duplicate PV	2016-05-16 14:40:43 -05:00
lvmetad.c	pvscan: use process_each_vg for autoactivate	2016-05-23 11:57:32 -05:00
lvmetad.h	pvscan: use process_each_vg for autoactivate	2016-05-23 11:57:32 -05:00