From: Bernardo Innocenti <bernie@develer.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: lkml <linux-kernel@vger.kernel.org>,
Neil Conway <nconway_kernel@yahoo.co.uk>,
nfs@lists.sourceforge.net
Subject: Re: NFS client bug in 2.6.8-2.6.11
Date: Tue, 08 Mar 2005 10:26:09 +0100 [thread overview]
Message-ID: <422D6FB1.4050506@develer.com> (raw)
In-Reply-To: <1110264475.11712.30.camel@lade.trondhjem.org>
Trond Myklebust wrote:
> ty den 08.03.2005 Klokka 07:38 (+0100) skreiv Bernardo Innocenti:
>>
>>Two clients started showing the problem after
>>being upgraded from FC2 to FC3, while the server
>>remained unchanged.
>
> Can you produce tcpdumps to back that up?
>
> Neil's problem appeared rather to be server-related. Neither of us could
> reproduce his problem when the server was exporting an XFS partition.
Actually, I was mistaken: running a background "find / >/dev/null"
triggers the problem even on the old RedHat (2.4.26) and
Gentoo (2.6.11) clients.
> The other thing to try is to turn off subtree checking on the server.
It's already turned off on all shares. For the record, this is the
contents of my /etc/exportfs:
/home gss/krb5(rw,no_root_squash,no_subtree_check,async) beetle(rw,no_root_squash,no_subtree_check,async) deimos(rw,async,no_subtree_check,anonuid=134,anongid=100) haring(rw,async,no_subtree_check,anonuid=127,anongid=100) murphy(rw,async,no_subtree_check,anonuid=158,anongid=100) daneel(rw,async,no_subtree_check,anonuid=100,anongid=100) 10.0.0.0/8(rw,no_subtree_check,async)
/arc 10.0.0.0/8(rw,no_root_squash,no_subtree_check,async,anonuid=14,anongid=113)
#
# NFSv4
#
/export beetle(rw,fsid=0,no_root_squash,insecure,no_subtree_check,async)
/export 10.0.0.0/8(rw,fsid=0,insecure,no_subtree_check,async)
/export gss/krb5(rw,fsid=0,insecure,no_subtree_check,async)
/export/home beetle(rw,nohide,no_root_squash,insecure,no_subtree_check,async)
/export/home 10.0.0.0/8(rw,nohide,insecure,no_subtree_check,async)
/export/home gss/krb5(rw,nohide,no_root_squash,insecure,no_subtree_check,async)
/export/arc 10.0.0.0/8(rw,nohide,no_root_squash,insecure,no_subtree_check,async,anonuid=14,anongid=113)
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
next prev parent reply other threads:[~2005-03-08 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 4:53 NFS client bug in 2.6.8-2.6.11 Bernardo Innocenti
2005-03-08 5:30 ` Trond Myklebust
2005-03-08 6:38 ` Bernardo Innocenti
2005-03-08 6:47 ` Trond Myklebust
2005-03-08 9:26 ` Bernardo Innocenti [this message]
2005-03-08 7:03 ` Bernardo Innocenti
2005-03-08 8:56 ` Anders Saaby
2005-03-08 22:25 ` Bernardo Innocenti
-- strict thread matches above, loose matches on Subject: below --
2005-03-15 23:44 Neil Conway
2005-03-16 2:49 ` Bernardo Innocenti
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=422D6FB1.4050506@develer.com \
--to=bernie@develer.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nconway_kernel@yahoo.co.uk \
--cc=nfs@lists.sourceforge.net \
--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