Red Hat Bugzilla – Bug 1224215
nfs-ganesha: rmdir logs "remote operation failed: Stale file handle" even though the operation is successful
Last modified: 2016-01-19 01:14:21 EST
Description of problem: Even though the operation like rmdir is successfully deleting the directory in consideration the gfapi.log gets updated by logs such as "remote operation failed: Stale file handle" This is a spurious log, doesn't seem to be giving any meaning to any one. Version-Release number of selected component (if applicable): glusterfs-3.7.0-2.el6rhs.x86_64 nfs-ganesha-2.2.0-0.el6.x86_64 How reproducible: always Steps to Reproduce: 1. create a volume of type 6x2, start it 2. bring up nfs-ganesha, after completing the pre-requisites 3. mount the volume with vers=4 or vers=3 4. create a dir and rmdir the same dir Actual results: step4 is successful but gfapi.log reports [2015-05-22 10:37:52.314210] W [client-rpc-fops.c:506:client3_3_stat_cbk] 0-vol2-client-1: remote operation failed: Stale file handle [2015-05-22 10:37:52.314461] W [client-rpc-fops.c:506:client3_3_stat_cbk] 0-vol2-client-3: remote operation failed: Stale file handle [2015-05-22 10:37:52.314606] W [client-rpc-fops.c:506:client3_3_stat_cbk] 0-vol2-client-11: remote operation failed: Stale file handle [2015-05-22 10:37:52.314761] W [client-rpc-fops.c:506:client3_3_stat_cbk] 0-vol2-client-7: remote operation failed: Stale file handle [2015-05-22 10:37:52.314860] W [client-rpc-fops.c:506:client3_3_stat_cbk] 0-vol2-client-9: remote operation failed: Stale file handle [2015-05-22 10:37:52.314978] W [client-rpc-fops.c:506:client3_3_stat_cbk] 0-vol2-client-5: remote operation failed: Stale file handle ^C Expected results: logs should be meaning ful, it should match the operation that it is doing, present logs give a wrong impression of the system Additional info:
Need to investigate if logging at Warning is suitable, maybe this should be marked as Debug instead. Ganesha does remove first, and then stats the file-handle to update the attributes (like hard-link count). The stale file handle is expected in this case.
I am don't see the ESTALE logs with the similar test
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1495.html