Hello,

I'm not sure if this is the appropriate place to ask, but we're running libvirtd with the sanlock plugin.
Ater a while, I noticed the following in the sanlock logfile after I couldn't create a new VM:

838555 sanlock daemon started aio 1 10 renew 20 80 host 144ce1f8-ddf7-4139-8e97-291aeddd7b81.arqua time 1330086549
838556 s1 lockspace __LIBVIRT__DISKS__:13:/var/lib/libvirt/sanlock/__LIBVIRT__DISKS__:0
838616 s1:r1 resource __LIBVIRT__DISKS__:7cf11c7a5da5d530521646d738636e84:/var/lib/libvirt/sanlock/7cf11c7a5da5d530521646d738636e84:0 for 1,9,31377
838632 s1:r2 resource __LIBVIRT__DISKS__:b2ad1e0874ba7c316cc848d3e0a98439:/var/lib/libvirt/sanlock/b2ad1e0874ba7c316cc848d3e0a98439:0 for 2,12,31499
839477 s1 check_our_lease warning 60 last_success 839417
839478 s1 check_our_lease warning 61 last_success 839417
839479 s1 check_our_lease warning 62 last_success 839417
839480 s1 check_our_lease warning 63 last_success 839417
839481 s1 check_our_lease warning 64 last_success 839417
839482 s1 check_our_lease warning 65 last_success 839417
839483 s1 check_our_lease warning 66 last_success 839417
839484 s1 check_our_lease warning 67 last_success 839417
839485 s1 check_our_lease warning 68 last_success 839417
839486 s1 check_our_lease warning 69 last_success 839417
839487 s1 check_our_lease warning 70 last_success 839417
839488 s1 check_our_lease warning 71 last_success 839417
839489 s1 check_our_lease warning 72 last_success 839417
839490 s1 check_our_lease warning 73 last_success 839417
839491 s1 check_our_lease warning 74 last_success 839417
839492 s1 check_our_lease warning 75 last_success 839417
839493 s1 check_our_lease warning 76 last_success 839417
839494 s1 check_our_lease warning 77 last_success 839417
839495 s1 check_our_lease warning 78 last_success 839417
839496 s1 check_our_lease warning 79 last_success 839417
839497 s1 check_our_lease failed 80
841667 s1 renewed 841667 delta_length 2229 too long
841671 r3 cmd_acquire 1,9,7234 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__
841672 r4 cmd_acquire 2,10,7268 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__
841674 r5 cmd_acquire 2,10,7765 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__
841675 r6 cmd_acquire 1,9,7735 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__
842012 r7 cmd_acquire 1,9,8495 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__
842013 r8 cmd_acquire 1,9,8622 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__
842015 r9 cmd_acquire 1,9,9130 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__
842016 r10 cmd_acquire 1,9,9241 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__
842019 r11 cmd_acquire 1,9,9669 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__
842020 r12 cmd_acquire 2,10,9697 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__
842021 r13 cmd_acquire 1,9,10146 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__
842022 r14 cmd_acquire 1,9,10240 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__
842115 r15 cmd_acquire 1,9,10755 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__
842117 r16 cmd_acquire 1,9,11008 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__
842410 r17 cmd_acquire 1,9,11511 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__
842410 r18 cmd_acquire 1,9,11616 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__
843609 r19 cmd_acquire 1,9,12835 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__
843616 r20 cmd_acquire 1,9,13093 invalid lockspace found -1 failed 0 name __LIBVIRT__DISKS__

So for some reason, the lockspace became invalid (and it looks like the host lease was not renewed).
Running sanlock-1.8-2.el6.x86_64.

Anything else I can check?

Best regards,
Frido