Ian, Can you send me the whole log file? The trace output captures all locks granted/blocked etc. Just wanted to analyze the log from the start of the lock testing session (when you execute locktest.pl) to when the problem is seen.
Pavan ----- Original Message ----- From: "Ian Steinmetz" <ian_steinm...@cable.comcast.com> To: "Pavan Sondur" <pa...@gluster.com> Cc: gluster-users@gluster.org, "Shehjar Tikoo" <shehj...@gluster.com> Sent: Wednesday, May 12, 2010 10:57:14 PM Subject: RE: [Gluster-users] NFS file locks Pavan, I turned on logging, and ran the perl lockd script again. Below is the output during the file locking test. If I remount the share it reproduces the 1st two errors over again exactly the same but with different timestamps. [2010-05-12 12:23:11] N [common.c:375:pl_trace_release] locks: [RELEASE] Lockee = {ino=1139, fd=0xb5500770, path=/locktest.pl} [2010-05-12 12:23:12] N [common.c:375:pl_trace_release] locks: [RELEASE] Lockee = {ino=76, fd=0xb5500770, path=/lockfile} [2010-05-12 12:23:17] N [common.c:375:pl_trace_release] locks: [RELEASE] Lockee = {ino=76, fd=0xb5500770, path=/lockfile} [2010-05-12 12:23:22] N [common.c:375:pl_trace_release] locks: [RELEASE] Lockee = {ino=76, fd=0xb5500770, path=/lockfile} [2010-05-12 12:23:27] N [common.c:375:pl_trace_release] locks: [RELEASE] Lockee = {ino=76, fd=0xb5500770, path=/lockfile} [2010-05-12 12:23:32] N [common.c:375:pl_trace_release] locks: [RELEASE] Lockee = {ino=76, fd=0xb5500770, path=/lockfile} [2010-05-12 12:23:37] N [common.c:375:pl_trace_release] locks: [RELEASE] Lockee = {ino=76, fd=0xb5500770, path=/lockfile} [2010-05-12 12:23:42] N [common.c:375:pl_trace_release] locks: [RELEASE] Lockee = {ino=76, fd=0xb5500770, path=/lockfile} [2010-05-12 12:23:47] N [common.c:375:pl_trace_release] locks: [RELEASE] Lockee = {ino=76, fd=0xb5500770, path=/lockfile} [2010-05-12 12:23:52] N [common.c:375:pl_trace_release] locks: [RELEASE] Lockee = {ino=76, fd=0xb5500770, path=/lockfile} [2010-05-12 12:26:39] N [common.c:375:pl_trace_release] locks: [RELEASE] Lockee = {ino=1139, fd=0xb5500770, path=/locktest.pl} [2010-05-12 12:26:39] N [common.c:375:pl_trace_release] locks: [RELEASE] Lockee = {ino=76, fd=0xb5500770, path=/lockfile} [2010-05-12 12:27:21] N [common.c:375:pl_trace_release] locks: [RELEASE] Lockee = {ino=76, fd=0xb5500770, path=/lockfile} -- Ian Steinmetz -----Original Message----- From: Pavan Sondur [mailto:pa...@gluster.com] Sent: Wednesday, May 12, 2010 1:53 AM To: Steinmetz, Ian Cc: gluster-users@gluster.org; Shehjar Tikoo Subject: Re: [Gluster-users] NFS file locks Ian, Mandatory locking is not supported in 3.0.x releases. Even if you turn this option on, it does not in any way change any locking behavior in GlusterFS. You can perhaps try this, specifically for locking: Turn on an option in the locks translator - 'option trace on'. It prints debug information about locks which is useful for debugging. Send us the output and we'll see if a bug needs to be filed. Nevertheless, we'll try and reproduce it in-house. Pavan ----- Original Message ----- From: "Ian Steinmetz" <ian_steinm...@cable.comcast.com> To: "Shehjar Tikoo" <shehj...@gluster.com> Cc: gluster-users@gluster.org Sent: Wednesday, May 5, 2010 12:04:52 AM Subject: Re: [Gluster-users] NFS file locks Shehjar, Good catch on the typo, I fixed it an restarted. Still had the same issue. I also was able to get samba working, and file locking seems to work fine; however, with samba the file owner/group and priv aren't transferred to clients. This at least points to an issue with how NFS/FUSE/GLUSTER are working together. I'm also searching to see if I can find any other FUSE file systems that have had similar issues. -- Ian Steinmetz -----Original Message----- From: Shehjar Tikoo [mailto:shehj...@gluster.com] Sent: Tuesday, May 04, 2010 1:40 AM To: Steinmetz, Ian Cc: gluster-users@gluster.org Subject: Re: [Gluster-users] NFS file locks 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] > > r...@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 _______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users _______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users