Steinmetz, Ian wrote: > I've turned on debug logging for the server and client of GlusterFS and > amended them below. I've replaced the IP addresses with "x.x.x" and > left the last octet for security. It appears I'm able to lock the file > when I run the program directly on the gluster mount point, just not > when it's mounted via NFS. I checked and rpc.statd is running. One odd > thing, when I run the perl locking program directly on the mnt point, > it appears to work but spits out the following log message: > > [2010-05-03 09:16:39] D [read-ahead.c:468:ra_readv] readahead: > unexpected offset (4096 != 362) resetting This is nothing to worry about..just debugging output. ..... ..... ..... > > [glusterfsd server logfile during above testing] > > root at gluster02:/var/log/glusterfs# /usr/sbin/glusterfsd -p > /var/run/glusterfsd.pid -f /etc/glusterfs/glusterfsd.vol --log-file > /var/log/glusterfsd.log --debug -N ..... ..... ..... > Given volfile: > +----------------------------------------------------------------------- > -------+ > 1: volume posix > 2: type storage/posix > 3: option directory /data/export > 4: end-volume > 5: > 6: volume locks > 7: type features/locks > 8: option manditory on I'll continue looking into this but in the mean time you could test over NFS again with "manditory" changed to "mandatory". Let me know if that works. Thanks -Shehjar > 9: subvolumes posix > 10: end-volume
