No, it was finally fixed in 3.3 so it does per-byte locking rather than per-file. Justice -----Original Message----- From: Nathan Stratton [mailto:nathan at robotics.net] Sent: Thursday, April 19, 2012 8:56 AM To: Justice London Cc: 'Gerald Brandt'; 'gluster-users' Subject: Re: Gluster 3.2.6 for XenServer On Thu, 19 Apr 2012, Justice London wrote: > My suggestion is actually to not use Gluster currently for XenServer. > A bug I filed about two years ago for using Gluster as a XenServer > back-end was just fixed in 3.3. If you're going to use Gluster+Xen, use 3.3. > > As for NFS, make sure that you changed the NFS port to 2049 in the > configuration and that should fix pretty much the front-end issues > with Gluster and Xen. Is the self heal issue still there in 3.3 where the file needs to be locked to heal? ><> Nathan Stratton nathan at robotics.net http://www.robotics.net