Works when mounted with "-o nolock" option.
root@shishirng-laptop:/mnt/glusterfs/new# ./autogen.sh autom4te: cannot lock autom4te.cache/requests with mode 2: Permission denied autom4te: cannot lock autom4te.cache/requests with mode 2: Permission denied ..then it hangs err log (nfs): [2011-07-11 12:10:21.586049] I [client3_1-fops.c:2228:client3_1_lookup_cbk] 0-new-client-1: remote operation failed: Stale NFS file handle [2011-07-11 12:10:21.586199] I [client3_1-fops.c:2228:client3_1_lookup_cbk] 0-new-client-0: remote operation failed: Stale NFS file handle
With 3.2.2qa6 I'm seeing this issue. I mounted with -o nolock option cat /proc/mounts has following entry 10.1.10.21:hosdu /gmnt nfs rw,vers=3,rsize=65536,wsize=65536,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,addr=10.1.10.21 0 0 And I get following error while trying to build [root@client4 glusterfs]# ./autogen.sh autom4te: cannot open autom4te.cache/requests: Permission denied autoheader: /usr/bin/autom4te failed with exit status: 1 autom4te: cannot open autom4te.cache/requests: Permission denied autom4te: cannot open autom4te.cache/requests: Permission denied automake: autoconf failed with exit status: 1 autom4te: cannot open autom4te.cache/requests: Permission denied autoheader: /usr/bin/autom4te failed with exit status: 1 autom4te: cannot open autom4te.cache/requests: Permission denied autom4te: cannot open autom4te.cache/requests: Permission denied automake: autoconf failed with exit status: 1
Vishwanath, can you try it again? It worked for me
Please cleanup your installation and check. This issue was fixed (dht_access_cbk)