Hello forum, in context of implementing KVM with a storage backend based on an Equallogic iSCSI-SAN i am still concerned about how to thoroughly prevent data corruptions in a HA-deployment. In that context, i stumbled upon the "libvirt-lock-sanlock" plugin, as well as the "sanlock" rpm itself, which apparently aims at preventing the launching of a VM/guest on multiple hosts. If i got that right, this would obsolete the measure to employ a cluster filesystem? 0) To my (still limited beginner's) understanding, i expected pacemaker would control which VM is launched under current conditions; but still SANLock exist and apparently also is featured in RHEV... 1) Does anybody has experience, whether the approach via SANlock is the better option then facilitating a cluster file system on the VM? I personally favour this approach based on the perception, that the locking happens on infrastructure level, allowing the VM to stay completely unconscious of the storage implementation in the backend and using the stock ext4 which would be preferred. 2) Is all of this actually a topic at all, because an Equallogic is doing the storage hosting, and already controls concurrent access to the iSCSI volume attempted by cluster members sufficiently? Any hint would be appreciated, Best