Hello, I wonder what the "open error -1" / "release open_disk error" messages in sanlock.log actually mean. I saw these messages in the log on a KVM host that rebooted, and after running "/usr/sbin/virt-sanlock-cleanup" on that host. The resources where disks from 2 guests running on another KVM host. So in fact the disks are still in use, bot got cleaned up by the other KVM host because it thought they were not longer in use... Several questions: 1. Could this indicate a problem with the lease of these resources on the server that host these guests? 2. Is there a way to reregister these resources, because they are still in use (but not for sanlock it seems)? 3. Overall, is it a bad idea to run virt-sanlock-cleanup? Some entries from the log file: 538 s1:r35 resource __LIBVIRT__DISKS__:e133401bfdff6979f76d9544ec8a5529:/var/lib/libvirt/sanlock/e133401bfdff6979f76d9544ec8a5529:0 for 1,9,4218 539 open error -1 /var/lib/libvirt/sanlock/e133401bfdff6979f76d9544ec8a5529 539 r35 release open_disk error /var/lib/libvirt/sanlock/e133401bfdff6979f76d9544ec8a5529 598 s1:r40 resource __LIBVIRT__DISKS__:fc82f9999b5afddb8aee9955db9b3477:/var/lib/libvirt/sanlock/fc82f9999b5afddb8aee9955db9b3477:0 for 2,12,4230 598 open error -1 /var/lib/libvirt/sanlock/fc82f9999b5afddb8aee9955db9b3477 598 r40 release open_disk error /var/lib/libvirt/sanlock/fc82f9999b5afddb8aee9955db9b3477 598 s1:r42 resource __LIBVIRT__DISKS__:ff9b82672a4dd869f9c9b38a6cbe3900:/var/lib/libvirt/sanlock/ff9b82672a4dd869f9c9b38a6cbe3900:0 for 2,12,4232 598 open error -1 /var/lib/libvirt/sanlock/ff9b82672a4dd869f9c9b38a6cbe3900 598 r42 release open_disk error /var/lib/libvirt/sanlock/ff9b82672a4dd869f9c9b38a6cbe3900 -- Frido Roose