On 4/23/2013 2:39 AM, David Weber wrote:
We do something similar in a 2 node DRBD/OCFS2 setup in which the vm
images and the sanlock lockspace reside in the OCFS2 volume. We did a
thorough testing and didn't run into any major problems with fencing.
Problematic are of course all split-brain situations. The setup has now
ran since over a year. AFAIK OCFS2 handles fencing in a different
way than GFS2 so I don't know if this really helps you.
You could take a look at virtlockd which was included into libvirt
1.0.1. It is perhaps sufficient to your needs and doesn't need a
lockspace.
See:http://www.redhat.com/archives/libvir-list/2011-July/msg00337.html
Cheers
David
Thanks! I have seen issues with sanlock running ontop of GFS2 (like I
mentioned earlier), and have seen emails from dev's recommending not
hosting the Lockspace dir on the GFS2 volume. So, I'm just trying to Do
The Right Thing ©
Virtlockd looks interesting! Looks like it does host a lockspace
under/var/lib/virtlock, and it mentions you can just move this to your
shared storage to gain protection across multiple machines. I wonder how
well it handles a node being fenced and the locks left behind, and if it
handles I/O being blocked better than Sanlock.
Either way, CentOS is only up to 0.10.2 for libvirt, so that option
isn't available for our usage unfortunately.