I am having a problem on my replicated setup where files which are commonlyĪccessed from different clients (such as ~/.Xauthority) are returning "Staleįile handle" warning and subsequent errors. Usage wasn't concurrent, but within 10 seconds orĠ-homes-client-0: remote operation failed: No such file or directory Subject: Re: Stale file handle with FUSE client "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++ Our cluster, after the second or third time I see these in the Path: /aorth/.viminfoĠ-glusterfs-fuse: 72528783: OPEN() /aorth/.viminfo => -1 (No such file Operation failed: No such file or directory. Operation failed: No such file or directory This happened after using vim on several machines which share the same Volume ID: 38637fa1-7ef3-4e8d-ace9-8ff81bc8bed9īrick1: storage0:/mnt/gfs/storage0/sda1/homesīrick2: storage1:/mnt/gfs/storage1/sdb1/homesĬlients and servers are all running GlusterFS 3.4.2 on CentOS 6.4/5.Į138: Can't write viminfo file /home/aorth/.viminfo! The volume in question (homes) is configured like this: Other times Iĭon't see any entries in the log file at all. Within small time spans, like ~/.cpan/CPAN/M圜onfig.pm. W Ġ-glusterfs-fuse: 69684128: OPEN() /aorth/.Xauthority => -1 (No suchĪnd I've seen the issue happen also when accessing other shared files Our cluster, after the second or third time I see these in the client's In this case, trying to log in with `ssh -X` to a few compute nodes in Isn't necessarily concurrent, but within a minute or two. Returning "Stale file handle" warning and subsequent errors. I am having a problem on my replicated setup where files which areĬommonly accessed from different clients (such as ~/.Xauthority) are
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |