From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: Kris Vassallo <kris@linuxcertified.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
nfs@lists.sourceforge.net, Olaf Kirch <okir@suse.de>,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: Stale File handles keep coming back
Date: Fri, 06 May 2005 08:38:47 +0200 [thread overview]
Message-ID: <427B10F7.3090600@bio.ifi.lmu.de> (raw)
In-Reply-To: <1115252134.2523.87.camel@localhost.localdomain>
Kris Vassallo wrote
> Ok a question for you. Let me explain what I am noticing: As soon as a
> client gets the stale file error, I go to the actual NFS server, and do
> a ls in the directory in question. Then without doing anything else, the
> client does another ls and then the contents can be seen. I don't know
> exactly what an ls does that would make the clients suddenly work again.
>
> Are you able to do something similar?
No. The client still gets the stale handle. However, it works again
if I do "cd `pwd`" on the client. So, reading Tronds comment
> That client-side patch can do nothing to prevent errors from being
> returned if a server is erroneously generating ESTALE.
>
> It will just make it unnecessary to do the equivalent of "cd
> `pwd`" (i.e. rewalk the path) on the client once the server manages to
> sort itself out.
I'm a bit confused if this patch would help or not. I will test it.
This might be interesting for Olaf: The problem does not exist in the
kotd sles9-i386/SLES9_SP2_BRANCH/
cu,
Frank
--
Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17 Phone: +49 89 2180-4049
80333 Muenchen, Germany Fax: +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-05-06 6:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 21:07 Stale File handles keep coming back Kris Vassallo
2005-04-26 12:27 ` Neil Brown
2005-04-26 22:22 ` Kris Vassallo
2005-04-27 2:42 ` Neil Brown
2005-04-29 7:01 ` Frank Steiner
2005-04-29 8:00 ` Frank Steiner
2005-04-29 14:08 ` Trond Myklebust
2005-04-30 13:15 ` Frank Steiner
2005-04-30 16:29 ` Trond Myklebust
2005-05-02 6:24 ` Frank Steiner
2005-05-03 10:45 ` Frank Steiner
2005-05-03 11:11 ` Frank Steiner
2005-05-05 0:15 ` Kris Vassallo
2005-05-06 6:38 ` Frank Steiner [this message]
2005-05-09 6:04 ` Frank Steiner
2005-04-29 14:03 ` Frank Steiner
2005-05-03 21:21 ` Kris Vassallo
2005-05-04 5:44 ` Frank Steiner
2005-05-04 22:48 ` Kris Vassallo
2005-05-04 23:06 ` Trond Myklebust
2005-05-12 1:01 ` Kris Vassallo
2005-05-12 1:14 ` Neil Brown
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=427B10F7.3090600@bio.ifi.lmu.de \
--to=fsteiner-mail@bio.ifi.lmu.de \
--cc=kris@linuxcertified.com \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--cc=okir@suse.de \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.