search for: client3_1_lookup_cbk

...7:38.964243] I [client-handshake.c:453:client_set_lk_version_cbk] 0-gl-client-6: Server lk version = 1 [2012-06-18 08:57:38.964507] I [fuse-bridge.c:3376:fuse_init] 0-glusterfs-fuse: FUSE inited with protocol versions: glusterfs 7.13 kernel 7.16 [2012-06-18 09:16:48.692701] W [client3_1-fops.c:2630:client3_1_lookup_cbk] 0-gl-client-4: remote operation failed: Stale NFS file handle. Path: /tdlong/RILseq/makebam.commands (90193380-d107-4b6c-b02f-ab53a0f65148) [2012-06-18 09:16:48.693030] W [client3_1-fops.c:2630:client3_1_lookup_cbk] 0-gl-client-4: remote operation failed: Stale NFS file handle. Path: /tdlong/RILse...

...on the no-output node return with no error code. In that sense the failure is silent, but corrupts the data, which is dangerous. The only indication of error are errors (on the no output nodes) in the /var/log/distrib-glusterfs.log of the form: [2013-02-18 05:55:31.382279] E [client3_1-fops.c:2228:client3_1_lookup_cbk] 0-volume1-client-16: remote operation failed: Stale NFS file handle [2013-02-18 05:55:31.382302] E [client3_1-fops.c:2228:client3_1_lookup_cbk] 0-volume1-client-17: remote operation failed: Stale NFS file handle [2013-02-18 05:55:31.382327] E [client3_1-fops.c:2228:client3_1_lookup_cbk] 0-volume1-...

...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 [afr-common.c:1520:afr_set_root_inode_on_first_lookup] 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: Star...

Hi, I'm a bit curious of error messages of the type "remote operation failed: Stale NFS file handle". All clients using the file system use Gluster Native Client, so why should stale nfs file handle be reported? Regards, /jon -------------- next part -------------- An HTML attachment was scrubbed... URL:

...1881 #8 afr_lookup_cbk (frame=0x18d5ae4, cookie=0x0, this=<value optimized out>, op_ret=<value optimized out>, op_errno=<value optimized out>, inode=0x18d5b20, buf=0x7fffcb83ec50, xattr=0x7fc4f12e1818, postparent=0x7fffcb83ebe0) at afr-common.c:2044 #9 0x00007fc4ee066550 in client3_1_lookup_cbk (req=<value optimized out>, iov=<value optimized out>, count=<value optimized out>, myframe=0x7fc4f16f390c) at client3_1-fops.c:2636 #10 0x00007fc4f25ff4e5 in rpc_clnt_handle_reply (clnt=0x3b5c600, pollin=0x6ba00f0) at rpc-clnt.c:786 #11 0x00007fc4f25ffce0 in rpc_clnt_notify (tran...

...go to that brick and look at that file via the underlying nfs, it is fine. I had thought this might be a case of bad meta-pointers, but there are no such pointers on the other bricks. In our gluster log file I see the following error repeated [2012-02-24 13:58:15.507390] E [client3_1-fops.c:2228:client3_1_lookup_cbk] 0-gdata-client-2: remote operation failed: Structure needs cleaning [2012-02-24 13:58:15.507501] W [fuse-bridge.c:184:fuse_entry_cbk] 0-glusterfs-fuse: 176567027: LOOKUP() /projects/philex/PE/2010/Oct18/arch07/BalbacFull_250_200_03Mar_3.png => -1 (Structure needs cleaning) How do we fix this?...

...re executing our script. We often get the error message "no such file or directory" in SGE log and cannot do anything about it. flush-behind is already turned off. What's the next thing we should try? Error log on client is [2012-09-10 11:18:48.129102] W [client3_1-fops.c:2630:client3_1_lookup_cbk] 0-home-client-0: remote operation failed: Stale NFS file handle. Path: XXXXXXXXXXXXXX (488a7270-1039-473b-9122-ae07b9e2c617) [2012-09-10 11:18:48.129162] W [client3_1-fops.c:2630:client3_1_lookup_cbk] 0-home-client-1: remote operation failed: Stale NFS file handle. Path: XXXXXXXXXXXXXX (488a7270-1...

....153925] W [rpc-common.c:64:xdr_to_generic] (-->/opt/glusterfs/3.2.1/lib64/libgfrpc.so.0(rpc_clnt_notify+0x8d) [0x2ab7b9d8f68d] (-->/opt/glusterfs/3.2.1/lib64/libgfrpc.so.0(rpc_clnt_handle_reply+0xa2) [0x2ab7b9d8f492] (-->/opt/glusterfs/3.2.1/lib64/glusterfs/3.2.1/xlator/protocol/client.so(client3_1_lookup_cbk+0xc3) [0x2aaaab1beec3]))) 0-xdr: XDR decoding failed [2011-07-11 10:21:59.153951] E [client3_1-fops.c:2174:client3_1_lookup_cbk] 0-gluster-vol01-client-2: error [2011-07-11 10:21:59.153973] I [client3_1-fops.c:2228:client3_1_lookup_cbk] 0-gluster-vol01-client-2: remote operation failed: Invalid arg...

Dear all, Right out of the blue glusterfs is not working fine any more every now end the it stops working telling me, Endpoint not connected and writing core files: [root at tuepdc /]# file core.15288 core.15288: ELF 64-bit LSB core file AMD x86-64, version 1 (SYSV), SVR4-style, from 'glusterfs' My Version: [root at tuepdc /]# glusterfs --version glusterfs 3.2.0 built on Apr 22 2011