Linux NFS development
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: Tom H <tom-6kxvdouIZplzjhtm8Ag3mw@public.gmane.org>
Cc: nfs@lists.sourceforge.net
Subject: Re: [NFS] Stale NFS file handle error
Date: Fri, 11 Jul 2008 09:38:40 -0400	[thread overview]
Message-ID: <48776260.5010503@redhat.com> (raw)
In-Reply-To: <48775EBC.4090008-6kxvdouIZplzjhtm8Ag3mw@public.gmane.org>

Tom H wrote:
> Peter Staubach wrote:
>   
>> Are you sure that you don't have two (or more) different NFS
>> clients working in the same directory?
>>
>> The ESTALE error usually occurs when a change is made on the
>> server to something that a client is accessing, perhaps
>> directly on the server or more commonly, by a different NFS
>> client.
>>     
>
> I'm as sure as I can be that the app is not opening the file multiple 
> times, the previous lines of code actually generate the folder and its 
> all sequential. The file names are all deterministic, only 1 process 
> running and nothing else accesses those files on the server. I have 
> checked for things like backup processes.
>
> It happens so infrequently that I get the feeling that its more likely 
> something else.
>
> I guess that I am looking for ways to troubleshoot the problem, maybe 
> with debug tools or whatever the guru nfs people would use...

It sounds like you are only using 1 NFS client?  Do you have
the same file system from the server mounted in more than one
place on this client?

You could try using something like tshark or tcpdump to capture
the network traffic when the error occurs, but I suspect that
if it really only happens infrequently, then you would end up
with gigabytes of capture and may or may not actually be able to
identify the traffic when the problem occurs.

Alternately, when the problem occurs, see if the file being
accessed really does continue to exist and is the same file,
ie. wasn't removed and then a new file with the same name
created in its place.

       ps

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
    http://vger.kernel.org/vger-lists.html#linux-nfs


      parent reply	other threads:[~2008-07-11 13:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-11 11:30 [NFS] Stale NFS file handle error Tom H
     [not found] ` <48774466.508-6kxvdouIZplzjhtm8Ag3mw@public.gmane.org>
2008-07-11 12:50   ` Peter Staubach
2008-07-11 13:23     ` Tom H
     [not found]       ` <48775EBC.4090008-6kxvdouIZplzjhtm8Ag3mw@public.gmane.org>
2008-07-11 13:38         ` Peter Staubach [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48776260.5010503@redhat.com \
    --to=staubach@redhat.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=tom-6kxvdouIZplzjhtm8Ag3mw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox