[Linux-cluster] GFS bug with fcntl/flock ?

[Robert Peterson]

Robert Hurst wrote:
> I am running InterSystems Caché 5.0.19 for AMD64, and an strace output 
> from their utility reveals a problem with fcntl/flock on the GFS 
> filesystem (mount -t gfs /dev/VGSHARE/lvol0 /usr/local):
>
>     open("/usr/local/etc/cachesys/cache.reg", O_RDONLY|O_NONBLOCK) = 3
>     fcntl(3, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0,
>     len=0}) = -1 ENOLCK (No locks available)
>
>
> When I put their files on an ordinary ext3 filesystem, all works fine:
>
>     open("/usr/local/etc/cachesys/cache.reg", O_RDONLY|O_NONBLOCK) = 3
>     fcntl(3, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0,
>     len=0}) = 0
>
>
> The man page on fcntl states that when flock is setup with 
> whence=SEEK_SET, start=0, and len=0, the lock will occur on the entire 
> file... so locking zero bytes in this manner is acceptable.  Help?
Hi Robert,

What version of the cluster software and GFS are you using?

Regards,

Bob Peterson
Red Hat CLuster Suite