Hello,<div><br></div><div>I configured libvirtd with the sanlock lock manager plugin:</div><div><br></div><div><div># rpm -qa | egrep &quot;libvirt-0|sanlock-[01]&quot;</div><div>libvirt-lock-sanlock-0.9.4-23.el6_2.4.x86_64</div>
<div>sanlock-1.8-2.el6.x86_64</div><div>libvirt-0.9.4-23.el6_2.4.x86_64</div></div><div><br></div><div><div># egrep -v &quot;^#|^$&quot; /etc/libvirt/qemu-sanlock.conf </div><div>auto_disk_leases = 1</div><div>disk_lease_dir = &quot;/var/lib/libvirt/sanlock&quot;</div>
<div>host_id = 4</div></div><div><br></div><div><div># mount | grep sanlock</div><div>/dev/mapper/kvm--shared-sanlock on /var/lib/libvirt/sanlock type gfs2 (rw,noatime,hostdata=jid=0)</div></div><div><br></div><div><div># cat /etc/sysconfig/sanlock </div>
<div>SANLOCKOPTS=&quot;-R 1 -o 30&quot;</div></div><div><br></div><div>I increased the sanlock io_timeout to 30 seconds (default = 10), because the sanlock dir is on a GFS2 volume and can be blocked for some time while fencing and journal recovery takes place.</div>
<div>With the default sanlock io timeout, I get lease timeouts because IO is blocked:</div><div><div><div>   Mar  5 15:37:14 raiti sanlock[5858]: 3318 s1 check_our_lease warning 79 last_success 3239</div><div>   Mar  5 15:37:15 raiti sanlock[5858]: 3319 s1 check_our_lease failed 80</div>
</div></div><div><br></div><div>So far, all fine, but when I restart sanlock and libvirtd, it takes about 2 * 30 seconds = 1 minute before libvirtd is usable.  &quot;virsh list&quot; hangs during this time.  I can still live with that...</div>
<div>But it gets worse after a reboot, when running a &quot;virsh list&quot; even takes a couple of minutes (like about 5 minutes) before it responds.  After this initial time, virsh is responding normally, so it looks like an initialization issue to me.</div>
<div><br></div><div>Is this a configuration issue, a bug, or expected behavior?</div><div><br></div><div>Thanks for any advice...</div><div>Frido</div>