Red Hat Bugzilla – Bug 851381
Failed to access the directory, "Stale NFS file handle"
Last modified: 2016-02-17 19:19:45 EST
Description of problem:
Could not access the directory.
> ls -l dir
??????????? ? ? ? ? ? dir
Setup a simple volume on your system.
Steps to Reproduce:
1.Mount the volume at mnt1
2.Mount the volume at another directory named mnt2
3.Open a console at mnt1, then 'mkdir dir; cd dir', stay there.
4.Open another console at mnt2, then 'rm -r dir; mkdir dir'(rebuild the dir)
5.Open third console at mnt1, then 'ls -l dir', you will see many '?'.
some error messages in log file:
[2012-08-23 08:41:10.613511] W [client-rpc-fops.c:2604:client3_3_lookup_cbk] 0-qe-client-0: remote operation failed: Stale NFS file handle. Path: /dir (92bb196c-6cb5-41af-a90f-2850f8d7ead6)
[2012-08-23 08:41:10.615441] W [client-rpc-fops.c:525:client3_3_stat_cbk] 0-qe-client-0: remote operation failed: No such file or directory
[2012-08-23 08:41:10.615468] W [fuse-bridge.c:590:fuse_attr_cbk] 0-glusterfs-fuse: 59: STAT() <gfid:92bb196c-6cb5-41af-a90f-2850f8d7ead6> => -1 (No such file or directory)
[2012-08-23 08:41:13.065630] W [client-rpc-fops.c:525:client3_3_stat_cbk] 0-qe-client-0: remote operation failed: No such file or directory
Try to reproduce it and see if attribute-timeout=0 option can fix the behavior.
This bug is fixed in upstream, though I don`t know which patch fixed it.
sorry for the rush, the bug is still there. I forgot to use the third console.
The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug.
If there has been no update before 9 December 2014, this bug will get automatocally closed.