Hi,
My bosses are running into an issue, where we type "ls" on a nfs mounted filesystem, and files that are there are not listed... I thought it was pilot error until my big boss showed me...
but we can vi the files, we can access them via other means if we know the name. Then once we have accessed them, LS now shows the files.
We are running centos 6.5, we are accessing them via xwin-32 (which should not be the issue)....
I looked on google and found nothing discussing this...of course this has nothing to do with hidden files (dot in front) because once we access the files we can see them.
Thanks Dan
On Mon, 22 Sep 2014 10:48:32 -0500 Dan Hyatt wrote:
but we can vi the files, we can access them via other means if we know the name. Then once we have accessed them, LS now shows the files.
Sounds like a caching issue to me. After you have accessed the file, it's in the cache and you can see it.
On 2014-09-22, Frank Cox theatre@melvilletheatre.com wrote:
On Mon, 22 Sep 2014 10:48:32 -0500 Dan Hyatt wrote:
but we can vi the files, we can access them via other means if we know the name. Then once we have accessed them, LS now shows the files.
Sounds like a caching issue to me. After you have accessed the file, it's in the cache and you can see it.
More specifically, it sounds like a client-side caching issue. I've seen this happen on linux clients if I'm *really* fast on the trigger.
--keith
So how do I fix it.
We actually have a widespread problem with files and directories "disappearing"... as it is one user in particular it might be pilot error, but it might be this. Because this is happening to two competent users.
On 9/22/2014 1:11 PM, Keith Keller wrote:
On 2014-09-22, Frank Cox theatre@melvilletheatre.com wrote:
On Mon, 22 Sep 2014 10:48:32 -0500 Dan Hyatt wrote:
but we can vi the files, we can access them via other means if we know the name. Then once we have accessed them, LS now shows the files.
Sounds like a caching issue to me. After you have accessed the file, it's in the cache and you can see it.
More specifically, it sounds like a client-side caching issue. I've seen this happen on linux clients if I'm *really* fast on the trigger.
--keith
On Mon, 22 Sep 2014 15:12:07 -0500 Dan Hyatt wrote:
but we can vi the files, we can access them via other means if we know the name. Then once we have accessed them, LS now shows the files.
Sounds like a caching issue to me. After you have accessed the file, it's in the cache and you can see it.
More specifically, it sounds like a client-side caching issue. I've seen this happen on linux clients if I'm *really* fast on the trigger.
So how do I fix it.
We actually have a widespread problem with files and directories "disappearing"... as it is one user in particular it might be pilot error, but it might be this. Because this is happening to two competent users.
Is fs-cache enabled?
Have you read this:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/htm...
On 2014-09-22, Dan Hyatt dhyatt@dsgmail.wustl.edu wrote:
So how do I fix it.
If it is in fact client-side, you have to fix the client. If these are Windows NFS clients then I am not much help. Perhaps the maintainers of the NFS client software have heard of this issue.
If you have Samba already set up, it might be interesting to see if the issue shows up there too. If it does, then it may not be a client-side issue. If it doesn't happen under Samba then it's more likely to be client-side NFS.
--keith
No it is not windows FS, this is a Hitachi Storage array managed by RedHat storage nodes.
How do I clear client side NFS without a reboot (sorry about the cross post)
For server side, it is simple service nfs restart. But it looks like redhat/centos no longer has a nfs client service.
On 9/22/2014 6:09 PM, Keith Keller wrote:
On 2014-09-22, Dan Hyatt dhyatt@dsgmail.wustl.edu wrote:
So how do I fix it.
If it is in fact client-side, you have to fix the client. If these are Windows NFS clients then I am not much help. Perhaps the maintainers of the NFS client software have heard of this issue.
If you have Samba already set up, it might be interesting to see if the issue shows up there too. If it does, then it may not be a client-side issue. If it doesn't happen under Samba then it's more likely to be client-side NFS.
--keith
-
Dan Hyatt -
Frank Cox -
Keith Keller