Stale file handle with FUSE client

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi, all.

I am having a problem on my replicated setup where files which are commonly accessed from different clients (such as ~/.Xauthority) are returning "Stale file handle" warning and subsequent errors.  Access isn't necessarily concurrent, but within a minute or two.

In this case, trying to log in with `ssh -X` to a few compute nodes in our cluster, after the second or third time I see these in the client's log file:

[2014-03-07 09:19:04.187240] W [client-rpc-fops.c:2624:client3_3_lookup_cbk] 0-homes-client-0: remote operation failed: Stale file handle. Path: /aorth/.Xauthority (79f4688e-da1b-4c0e-ae45-ac339f09d581)
[2014-03-07 09:19:04.187585] W [client-rpc-fops.c:2624:client3_3_lookup_cbk] 0-homes-client-1: remote operation failed: Stale file handle. Path: /aorth/.Xauthority (79f4688e-da1b-4c0e-ae45-ac339f09d581)
[2014-03-07 09:19:21.820247] W [client-rpc-fops.c:2624:client3_3_lookup_cbk] 0-homes-client-0: remote operation failed: Stale file handle. Path: /aorth/.Xauthority (d5bfeb33-786f-45ca-a533-a23cf0c54216)
[2014-03-07 09:19:21.820410] W [client-rpc-fops.c:2624:client3_3_lookup_cbk] 0-homes-client-1: remote operation failed: Stale file handle. Path: /aorth/.Xauthority (d5bfeb33-786f-45ca-a533-a23cf0c54216)
[2014-03-07 09:27:02.426186] W [client-rpc-fops.c:471:client3_3_open_cbk] 0-homes-client-0: remote operation failed: No such file or directory. Path: /aorth/.Xauthority (323ef093-1e18-463b-8544-0faf8b631985)
[2014-03-07 09:27:02.426517] W [client-rpc-fops.c:471:client3_3_open_cbk] 0-homes-client-1: remote operation failed: No such file or directory. Path: /aorth/.Xauthority (323ef093-1e18-463b-8544-0faf8b631985)
[2014-03-07 09:27:02.428410] W [fuse-bridge.c:915:fuse_fd_cbk] 0-glusterfs-fuse: 69684128: OPEN() /aorth/.Xauthority => -1 (No such file or directory)

And I've seen the issue happen also when accessing other shared files within small time spans, like ~/.cpan/CPAN/MyConfig.pm.  Other times I don't see any entries in the log file at all...

The volume in question (homes) is configured like this:
# gluster volume info homes
 
Volume Name: homes
Type: Replicate
Volume ID: 38637fa1-7ef3-4e8d-ace9-8ff81bc8bed9
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: storage0:/mnt/gfs/storage0/sda1/homes
Brick2: storage1:/mnt/gfs/storage1/sdb1/homes
Options Reconfigured:
nfs.disable: on
Clients and servers are all running GlusterFS 3.4.2 on CentOS 6.4/5.

Thanks,
-- 
Alan Orth
alan.orth@xxxxxxxxx
http://alaninkenya.org
http://mjanja.co.ke
"I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone." -Bjarne Stroustrup, inventor of C++
GPG public key ID: 0x8cb0d0acb5cd81ec209c6cdfbd1a0e09c2f836c0

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux