GFS bug with fcntl/flock ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?


Robert Hurst, Sr. Caché Administrator
Beth Israel Deaconess Medical Center
1135 Tremont Street, REN-7
Boston, Massachusetts   02120-2140
617-754-8754 ∙ Fax: 617-754-8730 ∙ Cell: 401-787-3154
Any technology distinguishable from magic is insufficiently advanced.
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux