2007/10/22, Kevan Benson <[EMAIL PROTECTED]>:
>
> Vincent Régnard wrote:
> > Using this latter script reveals that locking is working fine :)). Using
> > my program properly also works. I was actually removing the lock file
> > when it was locked by another instance ! So my programm was misbehaving
Vincent Régnard wrote:
Using this latter script reveals that locking is working fine :)). Using
my program properly also works. I was actually removing the lock file
when it was locked by another instance ! So my programm was misbehaving
after that. But the question is "why is it possible to remo
Kevan Benson a écrit :
Vincent Régnard wrote:
Anand Avati a écrit :
Kevan,
I just submitted a patch to fuse-devel which adds flock() support to
fuse.
You could either wait for the next fuse release, or install glusterfs's
patched fuse (2.7.0-glfs3) which has that patch included.
thanks,
ava
Vincent Régnard wrote:
Anand Avati a écrit :
Kevan,
I just submitted a patch to fuse-devel which adds flock() support to
fuse.
You could either wait for the next fuse release, or install glusterfs's
patched fuse (2.7.0-glfs3) which has that patch included.
thanks,
avati
I run a small appli
Are you sure you have 'features/posix-locks' translator loaded? because the
locking feature is provided by that translator. Without that, surely its not
going to work.
-amar
On 10/19/07, Vincent Régnard <[EMAIL PROTECTED]> wrote:
>
> Anand Avati a écrit :
> > Kevan,
> > I just submitted a patch
Anand Avati a écrit :
Kevan,
I just submitted a patch to fuse-devel which adds flock() support to fuse.
You could either wait for the next fuse release, or install glusterfs's
patched fuse (2.7.0-glfs3) which has that patch included.
thanks,
avati
I run a small application that uses flock on
Kevan,
I just submitted a patch to fuse-devel which adds flock() support to fuse.
You could either wait for the next fuse release, or install glusterfs's
patched fuse (2.7.0-glfs3) which has that patch included.
thanks,
avati
2007/8/7, Kevan Benson <[EMAIL PROTECTED]>:
>
>
> Any consensus on whe
Any consensus on whether flock support is planned for the future? I seem to
remember reading somewhere in the documentation that a native glusterfs
client was being considered at some point in the future, which could make
this feasible.
On Monday 06 August 2007 09:27, Amar S. Tumballi wrote:
Thanks for pointing out the mistakes in wiki.. just corrected it.
-amar
On 8/6/07, Kevan Benson <[EMAIL PROTECTED]> wrote:
>
> On Sunday 05 August 2007 23:28, Vikas Gorur wrote:
> > What you're trying to do is use flock(2) locks. flock(2) locks are not
> > supported by FUSE. The lock requests wil
On Sunday 05 August 2007 23:28, Vikas Gorur wrote:
> What you're trying to do is use flock(2) locks. flock(2) locks are not
> supported by FUSE. The lock requests will be handled by the kernel
> itself and never reach FUSE, let alone GlusterFS.
>
> The posix-locks translator implements the fcntl(2)
Forgot to CC: list.
-- Forwarded message --
From: Vikas Gorur <[EMAIL PROTECTED]>
Date: 05-Aug-2007 12:19
Subject: Re: [Gluster-devel] posix-locks problem
To: Kevan Benson <[EMAIL PROTECTED]>
On 04/08/07, Kevan Benson <[EMAIL PROTECTED]> wrote:
> I'
FYI, fuse version is 2.6.9.
On Friday 03 August 2007 14:49, Kevan Benson wrote:
> I'm having a problem getting locking to work, and this is with TLA patched
> to 425.
>
> Whenever I specify posix locks, I see this in the logs:
> [xlator.c:154:xlator_set_type] libglusterfs/xlator: dlsym(notify) on
I'm having a problem getting locking to work, and this is with TLA patched to
425.
Whenever I specify posix locks, I see this in the logs:
[xlator.c:154:xlator_set_type] libglusterfs/xlator: dlsym(notify) on
/opt/glusterfs-server/lib/glusterfs/1.3.0/xlator/features/posix-locks.so:
undefined sy
13 matches
Mail list logo
