mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Jakob Oestergaard <jakob@unthought.net>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	Brad Campbell <brad@wasp.net.au>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: nfs stale filehandle issues with 2.6.10-rc1 in-kernel server
Date: Thu, 04 Nov 2004 21:47:57 -0500	[thread overview]
Message-ID: <418AE9DD.3010008@pobox.com> (raw)
In-Reply-To: <20041102200925.GA12752@unthought.net>

Jakob Oestergaard wrote:
> On Tue, Nov 02, 2004 at 02:49:53PM -0500, Jeff Garzik wrote:
> 
>>Trond Myklebust wrote:
> 
> ...
> 
>>> http://nfs.sourceforge.net/nfs-howto/server.html#CONFIG
>>
>>
>>I'm also seeing stale filehandle problems here in recent kernels.
>>
>>Setup:  x86 or x86-64, TCP, NFSv4 compiled in to both server and client, 
>>but not specified in mount options.
>>
>>This is readily reproducible with rsync -- I just boot to an earlier 
>>version of the kernel on the NFS client, and the stale filehandle 
>>problems go away.
> 
> 
> Hi Jeff,
> 
> Does running an 'ls' on the server in the exported directory that is
> stale on the client resolve the problem (temporarily)?

Yes.

	Jeff




  reply	other threads:[~2004-11-05  2:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02 12:02 Brad Campbell
2004-11-02 16:37 ` Trond Myklebust
2004-11-02 19:49   ` Jeff Garzik
2004-11-02 20:09     ` Jakob Oestergaard
2004-11-05  2:47       ` Jeff Garzik [this message]
2004-11-05  2:59         ` Trond Myklebust
2004-11-05  3:07           ` Jeff Garzik
2004-11-05 13:43         ` Jakob Oestergaard
2004-11-02 21:05     ` Jeff V. Merkey
2004-11-02 21:37       ` Trond Myklebust
     [not found]         ` <20041102225304.GA11441@galt.devicelogics.com>
2004-11-03  0:19           ` Jeff V. Merkey
2004-11-03  1:13             ` Trond Myklebust
2004-11-03 16:54               ` Jeff V. Merkey
2004-11-03 21:38                 ` Jeff V. Merkey
2004-11-03 23:32                   ` Trond Myklebust
2004-11-04  0:12                     ` Jeff V. Merkey
2004-11-02 21:36     ` Trond Myklebust
2004-11-05  2:57       ` Jeff Garzik
2004-11-05  3:09         ` Trond Myklebust
2004-11-05  7:27           ` Jeff Garzik
2004-11-02 21:51     ` J. Bruce Fields
2004-11-08 20:53       ` J. Bruce Fields
2004-11-03 15:10   ` Jakob Oestergaard
2004-11-03 16:02     ` J. Bruce Fields
2004-11-03 16:05     ` Trond Myklebust

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=418AE9DD.3010008@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=brad@wasp.net.au \
    --cc=jakob@unthought.net \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome