When a hypervisor was rebooted all LVs which were part of a FC storage domain were automatically activated. This was cause some issues on occasion, as logical volumes should by activated only on request of the engine if needed (VM start), and deactivate immediately when the LVs are not needed (VM stop). This happened because when using FC storage, physical volumes are connected during boot, and vdsm. Logical volumes are auto-activated by both /etc/rc.sysinit and /etc/init.d/netfs startup scripts. These logical volumes did not pick changes done by the SPM on the storage, which could eventually lead to data corruption when a vm is trying to write to the logical volume with stale meta data.
The fix checks all vdsm logical volumes during lvm bootstrap and deactivates them if possible. Special logical volumes are refreshed, since they are accessed early when connecting to storage pool, possibly before lvm bootstrap is done. Open logical volumes are skipped because it is assumed that they use correct meta data when opened.