Hi Paul,
Locking is part of the core GlusterFS protocol but the NFS server module
does not have NLM support yet(NLM is the locking protocol associated with
NFSv3). On linux, the workaround is generally to mount with the -o nolock
option although I dont see why excluding this option results in stale file
handle and other errors. let me go through the complete thread, I'll reply
elsewhere.
Today, if locking among multiple client machines is a must-have, you'll
have to use FUSE.
paul simpson wrote:
so, while your all about - my big question is can/does gluster (with
NFS/fuse client) properly lock files?
ie, a simple test is to checkout a svn tree to a gluster, modify, checkin,
list, alter, revert. everytime i do this with 3.1.2 i get input/output
errors from my client machine within a few minutes.
------------------------------------------------------------------------
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
