Hi!
you need to use fuse.ko from fuse-2.6.x from fuse.sf.net.
the standard kernels' fuse dont support locking as the 2.6 fuse is not
yet merged into mainstream kernel.
Also locking code is undergoing some changes so please keep using the
tla checkout rather than the tarball.
regards,
avati
On Wed, Mar 28, 2007 at 03:45:57PM +0200, gpvcs@xxxxxxxxxx wrote:
> Hi,
>
> First of all, I would like to say that I found GlusterFS
> being a great project with ingenious design. I tryied many
> different failover solutions (ocfs2, safekit, lustre, gfarm)
> and this one is the best.
>
> I'm trying to share a central file system between two
> clients using glusterfs 1.3.0pre2. Replication works
> perfectly but I have difficulties with locking.
> When I'm mounting the same filesystem (ie: same client.vol)
> on two machines, both machines are able to do an exclusive
> lock on the "same" file (ie: lock /gfs/fs1/toto) .
> I don't know if its a misconfiguration, a problem with my
> boxes (DLM ?, fuse ?), a bug or if that kind of locking is
> not yet implemented.
> I'm running Linux Fedora FC4 (2.6.17-1.2142_FC4).
>
> When I'm tracing the code I dont see the fuse_getlk or the
> fuse_setlk being called contrary to fuser_readdir.
> client_protocol:client_lk never called
> proto-srv.c:fop_lk never called.
>
> I would really appreciate some help on this issue.
>
> Regards FT
>
--
Shaw's Principle:
Build a system that even a fool can use,
and only a fool will want to use it.
