+++ This bug was initially created as a clone of Bug #1224215 +++
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):
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
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
logs should be meaning ful, it should match the operation that it is doing, present logs give a wrong impression of the system
--- Additional comment from Niels de Vos on 2015-06-05 14:27:31 CEST ---
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.
REVIEW: http://review.gluster.org/11169 (logging: log "Stale filehandle" on the client as Debug) posted (#2) for review on release-3.7 by Kaleb KEITHLEY (email@example.com)
COMMIT: http://review.gluster.org/11169 committed in release-3.7 by Vijay Bellur (firstname.lastname@example.org)
Author: Niels de Vos <email@example.com>
Date: Thu Jun 11 01:07:56 2015 +0200
logging: log "Stale filehandle" on the client as Debug
There are valid use-cases where a "Stale filehandle" is expected. One of
these is deleting a file through NFS-Ganesha. When the "filename" is
deleted, Ganesha will stat the file-handle to update its attributes. The
file-handle would still be valid in the case where there are hardlinks.
There is no need to log "Stale filehandle" as Warning. It is perfectly
fine to have this logged as Debug.
Cherry picked from commit ec7d0c3de11cbee1470308dcc10ec9f02e7fdfff:
> Change-Id: Ib9006d95a5d1f7dd394bf5d5994ad70740ad4ab2
> BUG: 1228731
> Signed-off-by: Niels de Vos <firstname.lastname@example.org>
> Reviewed-on: http://review.gluster.org/11107
> Reviewed-by: Kaleb KEITHLEY <email@example.com>
> Tested-by: Gluster Build System <firstname.lastname@example.org>
> Reviewed-by: soumya k <email@example.com>
> Reviewed-by: jiffin tony Thottan <firstname.lastname@example.org>
Signed-off-by: Niels de Vos <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Vijay Bellur <email@example.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.2, please reopen this bug report.
glusterfs-3.7.2 has been announced on the Gluster Packaging mailinglist , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.