From: Jeff Garzik <jgarzik@pobox.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: 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: Tue, 02 Nov 2004 14:49:53 -0500 [thread overview]
Message-ID: <4187E4E1.5080304@pobox.com> (raw)
In-Reply-To: <1099413424.7582.5.camel@lade.trondhjem.org>
Trond Myklebust wrote:
> ty den 02.11.2004 Klokka 16:02 (+0400) skreiv Brad Campbell:
>
>
>>/raid 192.168.2.81(rw,async,no_root_squash)
>>/raid 192.168.3.80(rw,async,no_root_squash)
>>/raid0 192.168.2.81(rw,async,no_root_squash)
>>/raid0/tmp 192.168.2.81(rw,async,no_root_squash)
>>/raid2 192.168.2.81(rw,async,no_root_squash)
>>/raid2 192.168.3.80(rw,async,no_root_squash)
>>/nfsroot 192.168.2.81(rw,async,no_root_squash)
>
>
> You should only have 1 line per directory.
>
> You are not allowed to export a directory and its child (unless the
> child is on a different partition - which does not appear to be the case
> here).
>
> 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.
JEff
next prev parent reply other threads:[~2004-11-02 19:51 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 [this message]
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
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=4187E4E1.5080304@pobox.com \
--to=jgarzik@pobox.com \
--cc=brad@wasp.net.au \
--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