From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Kris Vassallo <kris@linuxcertified.com>, nfs@lists.sourceforge.net
Subject: Re: Stale File handles keep coming back
Date: Fri, 29 Apr 2005 16:03:23 +0200 [thread overview]
Message-ID: <42723EAB.3070103@bio.ifi.lmu.de> (raw)
In-Reply-To: <17006.64544.860436.620665@cse.unsw.edu.au>
One more info:
It seems that we can easily reproduce the problem when
a) an application does some work in a directory and
b) a shell is running in the same directory and left unused for some
time (about 45 minutes seem to be enough).
Then the shell encounters the "stale NFS handle" when it tries to do
sth again.
Scenarios are e.g. an emacs running and writing a .tex file every
few minutes, and a shell is used to call "latex ...". 40 minutes of
editing with emacs without using the shell result in a stale NFS
handle when calling latex in the shell after that time.
Or running a firefox and having the shell chdir to
~/.mozilla/firefox/<the defaults user profile directory>
I guess firefox is writing the cache or sth. else. Again, the shell
will stale when left untouched for about 40 minutes.
Maybe this can help to reproduce the bug.
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. *
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-04-29 14:05 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
2005-05-09 6:04 ` Frank Steiner
2005-04-29 14:03 ` Frank Steiner [this message]
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=42723EAB.3070103@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 \
/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.