Hi, 1) FYI: https://bugzilla.redhat.com/show_bug.cgi?id=1217576 I will need some help from a Gluster expert to debug this issue, since I don't know Gluster internals. On a replica-3 cluster with best practices, it's very frustrating to see the whole DC going down because of a FS lock. 2) Should we at some point freeze gluster updates and stick to a stable version, or are we following new features required by oVirt? I feel Gluster very unstable yet, but maybe it's just me. I guess that if a "stat" operation (mount, lsof, etc) of a gluster volume is locking, it's the layer below sanlock, right? I don't think that sanlock should be able to lock Gluster, does it? 3) My feature request: Sanlock+Gluster unit-tests written by the sanlock authors to stress and exploit all Gluster weaknesses. PS: The good news is that [1] and other related issues were finally fixed. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1201355 Best regards, Christopher.