On 11/21/2012 05:22 PM, David Teigland wrote:
On Wed, Nov 21, 2012 at 05:15:55PM +0100, sysadmin(a)albasoft.com
wrote:
> On this specific host it was running directly on ext4. I'll change
> it to nfs and report.
>
Aren't you using multiple hosts to run shared vm images?
If not, then using sanlock is pointless.
Yes, I am using multiple hosts and sharings vm.
But this was the nfs server host, so I thought there was no point in nfs
mounting a local path.
> That path is on ext4 filesystem on top of LVM2 logical volume on top
> of a md raid1 device. Does that say something to you?
>
ext4 or md are probably the cause of the problems; sanlock will not
work properly with either.
I'm running another set of 3 hosts with exactly the same arrangement
(ext4, lvm, md raid) for months, and I get no error.
The only log from sanlock I get is
Nov 17 18:01:50 storage02 kernel: EXT4-fs (dm-1): Unaligned AIO/DIO on
inode 1569995 by sanlock; performance will be poor.
but no "check_our_lease corrupt"