All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kris Vassallo <kris@linuxcertified.com>
To: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
	nfs@lists.sourceforge.net, Olaf Kirch <okir@suse.de>
Subject: Re: Stale File handles keep coming back
Date: Wed, 04 May 2005 17:15:34 -0700	[thread overview]
Message-ID: <1115252134.2523.87.camel@localhost.localdomain> (raw)
In-Reply-To: <42775C56.9000703@bio.ifi.lmu.de>

[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]


On Tue, 2005-05-03 at 04:11, Frank Steiner wrote:

> Frank Steiner wrote
> 
> > minutes. After this time, they do a "ls" and get
> > 
> > ls: .: Stale NFS file handle
> > 
> > Calling "cd .." and then "cd <former_directory>", the ls works
> > again.

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?

-Kris


> 
> We just figured out that the files in the directory can be viewed when
> doing "ls specific_file":
> 
> wirth [13:09] lx003umv.default 55) ls -la
> ls: .: Stale NFS file handle
> wirth [13:10] lx003umv.default 56) ls -la defaults.ini
> -rw-------    1 tester   users          24 Apr 29 13:10 defaults.ini
> wirth [13:10] lx003umv.default 57) ls -la
> ls: .: Stale NFS file handle
> 
> So just "." goes stale, everything below seems to be sane. Maybe that
> info is helpful...
> 
> cu,
> Frank

[-- Attachment #2: Type: text/html, Size: 1607 bytes --]

  reply	other threads:[~2005-05-05  0:15 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 [this message]
2005-05-06  6:38             ` Frank Steiner
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=1115252134.2523.87.camel@localhost.localdomain \
    --to=kris@linuxcertified.com \
    --cc=fsteiner-mail@bio.ifi.lmu.de \
    --cc=neilb@cse.unsw.edu.au \
    --cc=nfs@lists.sourceforge.net \
    --cc=okir@suse.de \
    /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.