ClusterSuite:
ccs-1.0.7-0.src.rpm ipvsadm-1.24-6.src.rpm
cman-1.0.11-0.src.rpm magma-1.0.6-0.src.rpm
cman-kernel-2.6.9-45.5.src.rpm magma-plugins-1.0.6-0.src.rpm
dlm-1.0.1-1.src.rpm perl-Net-Telnet-3.03-3.noarch.rpm
dlm-kernel-2.6.9-42.13.src.rpm piranha-0.8.2-1.src.rpm
fence-1.32.25-1.src.rpm rgmanager-1.9.53-0.src.rpm
gulm-1.0.7-0.src.rpm system-config-cluster-1.0.25-1.0.src.rpm
iddev-2.0.0-3.src.rpm
GFS:
GFS-6.1.6-1.src.rpm gnbd-kernel-2.6.9-9.44.src.rpm
GFS-kernel-2.6.9-58.3.src.rpm libsepol-devel-1.1.1-2.x86_64.rpm
gnbd-1.0.7-0.src.rpm lvm2-cluster-2.02.06-7.0.RHEL4.src.rpm
On Wed, 2006-10-11 at 08:20 -0500, Robert Peterson wrote:
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 -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
