Another invocation of this issue:
E138: Can't write viminfo file /home/aorth/.viminfo!
This happened after using vim on several machines which share the same
networked /home directory. Usage wasn't concurrent, but within 10
seconds or so of each other. The client's volume log looks like this:
Subject: Re: [Gluster-users] Stale file handle with FUSE client
Another invocation of this issue:
E138: Can't write viminfo file /home/aorth/.viminfo!
This happened after using vim on several machines which share the same
networked /home directory. Usage wasn't concurrent, but within 10
13, 2014 1:23:02 PM
Subject: Re: [Gluster-users] Stale file handle with FUSE client
Alan,
I could be wrong, but the issue looks so much like the following bug?
https://bugzilla.redhat.com/show_bug.cgi?id=1041109
Pranith
- Original Message -
From: Alan Orth alan.o...@gmail.com
pkara...@redhat.com
To: Alan Orth alan.o...@gmail.com
Cc: gluster-users gluster-users@gluster.org
Sent: Thursday, March 13, 2014 1:23:02 PM
Subject: Re: [Gluster-users] Stale file handle with FUSE client
Alan,
I could be wrong, but the issue looks so much like the following bug?
https
- Original Message -
From: Alan Orth alan.o...@gmail.com
To: Pranith Kumar Karampuri pkara...@redhat.com
Cc: gluster-users gluster-users@gluster.org
Sent: Thursday, March 13, 2014 2:13:26 PM
Subject: Re: [Gluster-users] Stale file handle with FUSE client
Hi, Pranith.
Let me re
PM
Subject: Re: [Gluster-users] Stale file handle with FUSE client
Hi, Pranith.
Let me re-mount the volumes on my nodes using use-readdirp=no and do
some more testing.
Also, one of the suggestions in that bug thread was to drop caches. I
did this on one of the clients in question
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
