From: Jeff Garzik <jgarzik@pobox.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Jakob Oestergaard <jakob@unthought.net>,
Brad Campbell <brad@wasp.net.au>,
lkml <linux-kernel@vger.kernel.org>,
"Dr. Bruce Fields" <bfields@fieldses.org>
Subject: Re: nfs stale filehandle issues with 2.6.10-rc1 in-kernel server
Date: Thu, 04 Nov 2004 22:07:57 -0500 [thread overview]
Message-ID: <418AEE8D.4010007@pobox.com> (raw)
In-Reply-To: <1099623541.25951.8.camel@lade.trondhjem.org>
Trond Myklebust wrote:
> to den 04.11.2004 Klokka 21:47 (-0500) skreiv Jeff Garzik:
>
>>>Does running an 'ls' on the server in the exported directory that is
>>>stale on the client resolve the problem (temporarily)?
>>
>>Yes.
>
>
> This still looks very much like a server issue to me. Could someone who
> is seeing the bug try to capture an instance of the ESTALE error going
> across the wire, and then do a fresh lookup of the same file from an
> "ls" call. I'd like to check how the stale filehandle differs from the
> freshly looked up one...
>
> Please use "tcpdump -s 9000 -w /tmp/binary.pcap port 2049 and host
> my.servers.name" for the actual capture.
Will do.
FWIW my server is running 2.6.9-final. Client mount options in fstab
are "defaults,tcp" and server options are (rw,no_root_squash,async).
Jeff
next prev parent reply other threads:[~2004-11-05 3:08 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
2004-11-05 2:59 ` Trond Myklebust
2004-11-05 3:07 ` Jeff Garzik [this message]
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=418AEE8D.4010007@pobox.com \
--to=jgarzik@pobox.com \
--cc=bfields@fieldses.org \
--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