[Gluster-users] remote operation failed: Stale NFS file handle

David Coulson david at davidcoulson.net
Wed Jan 25 03:24:09 UTC 2012

I've got a pretty simple Gluster 3.2.5 implementation on RHEL6. One 
client keeps complaining about 'Stale NFS file handle', even though I 
have explicitly disabled NFS for all volumes in the environment. I've 
got 7 volumes on the cluster, and this is the only one actively 
complaining about the issue. For what it is worth, the clients and 
servers are the same systems. Any ideas? I saw a few other people 
reporting the same issue with earlier releases of Gluster, but did not 
see a solution or further troubleshooting steps.

[2012-01-24 20:57:22.765190] I [fuse-bridge.c:3339:fuse_graph_setup] 
0-fuse: switched to graph 0
[2012-01-24 20:57:22.765314] I [fuse-bridge.c:2927:fuse_init] 
0-glusterfs-fuse: FUSE inited with protocol versions: glusterfs 7.13 
kernel 7.13
[2012-01-24 20:57:22.765710] I 
0-openfire-replicate-0: added root inode
[2012-01-24 22:15:44.984871] E 
[client3_1-fops.c:2228:client3_1_lookup_cbk] 0-openfire-client-0: remote 
operation failed: Stale NFS file handle
[2012-01-24 22:15:44.985228] E 
[client3_1-fops.c:2228:client3_1_lookup_cbk] 0-openfire-client-1: remote 
operation failed: Stale NFS file handle

# gluster volume info openfire

Volume Name: openfire
Type: Replicate
Status: Started
Number of Bricks: 2
Transport-type: tcp
Brick1: rhesproddns01:/gluster/openfire
Brick2: rhesproddns02:/gluster/openfire
Options Reconfigured:
nfs.register-with-portmap: off
nfs.disable: on


More information about the Gluster-users mailing list