Bug 762709 (GLUSTER-977)

Summary: [3.0.5rc3] Stale NFS file handle error
Product: [Community] GlusterFS Reporter: Anush Shetty <anush>
Component: replicateAssignee: Anush Shetty <anush>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: low    
Version: 3.0.4CC: amarts, gluster-bugs, vijay
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Anush Shetty 2010-06-02 12:01:04 UTC
Encountered this while doing `rm -rf` over a directory with 250000 over distributed-replicate mount point. The files were created using glfs-bm

[2010-06-02 16:48:51] T [fuse-bridge.c:2198:fuse_readdir_cbk] glusterfs-fuse: 3143198: READDIR => 2/4096,0
[2010-06-02 16:48:51] T [fuse-bridge.c:2252:fuse_readdir] glusterfs-fuse: 3143199: READDIR (0x7f8f70000ab0, size=4096, offset=4294967295)
[2010-06-02 16:48:51] T [fuse-bridge.c:2198:fuse_readdir_cbk] glusterfs-fuse: 3143199: READDIR => 0/4096,4294967295
[2010-06-02 16:48:51] T [fuse-bridge.c:2270:fuse_releasedir] glusterfs-fuse: 3143200: RELEASEDIR 0x7f8f70000ab0
[2010-06-02 16:48:51] D [client-protocol.c:4966:client_lookup_cbk] client2: LOOKUP 0/ (/): inode number changed from {5475526361105825793,1} to {5476238823165788161,1}
[2010-06-02 16:48:51] D [client-protocol.c:4966:client_lookup_cbk] client2: LOOKUP 0/ (/): inode number changed from {5475526361105825793,1} to {5476238823165788161,1}
[2010-06-02 17:21:32] D [client-protocol.c:4966:client_lookup_cbk] client2: LOOKUP 0/ (/): inode number changed from {5475526361105825793,1} to {5476238823165788161,1}
[2010-06-02 17:21:32] D [client-protocol.c:4966:client_lookup_cbk] client2: LOOKUP 0/ (/): inode number changed from {5475526361105825793,1} to {5476238823165788161,1}
[2010-06-02 17:21:33] D [client-protocol.c:4966:client_lookup_cbk] client2: LOOKUP 0/ (/): inode number changed from {5475526361105825793,1} to {5476238823165788161,1}
[2010-06-02 17:21:33] D [client-protocol.c:4966:client_lookup_cbk] client2: LOOKUP 0/ (/): inode number changed from {5475526361105825793,1} to {5476238823165788161,1}
[2010-06-02 17:21:35] D [client-protocol.c:4966:client_lookup_cbk] client2: LOOKUP 0/ (/): inode number changed from {5475526361105825793,1} to {5476238823165788161,1}
[2010-06-02 17:21:35] W [fuse-bridge.c:725:fuse_attr_cbk] glusterfs-fuse: 3143207: LOOKUP() / => -1 (Stale NFS file handle)
[2010-06-02 17:21:35] D [client-protocol.c:4966:client_lookup_cbk] client2: LOOKUP 0/ (/): inode number changed from {5475526361105825793,1} to {5476238823165788161,1}
[2010-06-02 17:21:36] D [client-protocol.c:4966:client_lookup_cbk] client2: LOOKUP 0/ (/): inode number changed from {5475526361105825793,1} to {5476238823165788161,1}
[2010-06-02 17:21:36] D [client-protocol.c:4966:client_lookup_cbk] client2: LOOKUP 0/ (/): inode number changed from {5475526361105825793,1} to {5476238823165788161,1}
[2010-06-02 17:21:37] D [client-protocol.c:4966:client_lookup_cbk] client2: LOOKUP 0/ (/): inode number changed from {5475526361105825793,1} to {5476238823165788161,1}
[2010-06-02 17:21:37] D [client-protocol.c:4966:client_lookup_cbk] client2: LOOKUP 0/ (/): inode number changed from {5475526361105825793,1} to {5476238823165788161,1}
[2010-06-02 17:21:37] T [fuse-bridge.c:2388:fuse_statfs] glusterfs-fuse: 3143213: STATFS
[2010-06-02 17:22:03] D [client-protocol.c:4966:client_lookup_cbk] client2: LOOKUP 0/ (/): inode number changed from {5475526361105825793,1} to {5476238823165788161,1}
[2010-06-02 17:22:03] D [client-protocol.c:4966:client_lookup_cbk] client2: LOOKUP 0/ (/): inode number changed from {5475526361105825793,1} to {547623882316

Comment 1 Vijay Bellur 2010-07-22 03:39:47 UTC
Please reproduce this bug with -L TRACE client and server logs with all statedumps.

Comment 2 Amar Tumballi 2010-10-05 07:36:42 UTC
This part of the logs will never happen with 3.1 now after bringing gfid changes. I will be closing this with WONTFIX.. please test with 3.1 releases and if the issue persists, re-open.