On Fri, Mar 2, 2012 at 3:52 PM, David Teigland <teigland@redhat.com> wrote:
On Fri, Mar 02, 2012 at 10:51:31AM +0100, Frido Roose wrote:
> On Tue, Feb 28, 2012 at 5:00 PM, David Teigland <teigland@redhat.com> wrote:
>
> > On Tue, Feb 28, 2012 at 04:40:04PM +0100, Frido Roose wrote:
> > > 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
> >
> > It looks like i/o to your storage blocked for 2229 seconds, which is much
> > longer than the 80 seconds it's given.  If this is on nfs, you might check
> > if the nfs server was down.
> >
> >
> Thanks for your quick reply.
> The lockspace is on a GFS2 volume, but you are right that we had an issue
> with the GFS2 volume that was hanging for some reason:

sanlock is designed to be used on a shared block device directly.
Using it on top of gfs2 doesn't make much sense.


That's how libvirtd implements it (http://libvirt.org/locking.html).  It expects a directory configured by the disk_lease_dir parameter, not a block device.
I don't see why NFS would make more sense than GFS2, since NFS also exports a directory?

The result is a shared disk over all cluster nodes:
# ls -l /var/lib/libvirt/sanlock/
total 13364
-rw------- 1 root root 1048576 Feb 24 14:53 144144defb21c092062750f6c91d91b4
-rw------- 1 root root 1048576 Feb 17 22:53 15b60674efbfa8ea119962de17968bbf
-rw------- 1 root root 1048576 Feb 28 16:48 5a229925efd128f4737bbb4e0772543a
-rw------- 1 root root 1048576 Mar  1 13:47 5a7bab89aefafd8460975ebdd18eab4d
-rw------- 1 root root 1048576 Feb 24 14:53 7cf11c7a5da5d530521646d738636e84
-rw------- 1 root root 1048576 Feb 28 16:22 a2f9ae7d144b7a2a01315db2fb278a09
-rw------- 1 root root 1048576 Feb 24 14:53 b2ad1e0874ba7c316cc848d3e0a98439
-rw------- 1 root root 1048576 Feb 28 16:45 c8c1d70159e8cc4b591e1b03eb525390
-rw------- 1 root root 1048576 Feb 28 16:50 ce9ddbfff85d9fa320ad12d752cc5a71
-rw------- 1 root root 1048576 Feb 27 16:08 d4c9f7bf3a6b41be8a501ac8362cf70f
-rw------- 1 root root 1048576 Feb 24 16:58 fc3d3741342f06ecbc642eddc165b4c6
-rw------- 1 root root 1048576 Feb 28 16:49 ff4710dfd7f79caeac8a87603ec312f2
-rw------- 1 root root 1048576 Mar  2 16:13 __LIBVIRT__DISKS__