From: hanasaki <hanasaki@hanaden.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Mike Fedyk <mfedyk@matchmail.com>,
nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [NFS] NFS rpc and stale handles on 2.6.x servers
Date: Thu, 29 Jan 2004 20:11:20 -0600 [thread overview]
Message-ID: <4019BD48.60905@hanaden.com> (raw)
In-Reply-To: <16409.46352.877421.233677@notabene.cse.unsw.edu.au>
Add this to your exportfs "no_subtree_check" It seems to be a temp
workaround. Searching the web, the only issue with this option seems to
be a minor performance hit (big issue for large systems). Any chance of
getting the patch 2.6.2? www.kernel.org looks like its still on an RC2
of this.
Neil Brown wrote:
> On Thursday January 29, mfedyk@matchmail.com wrote:
>
>>On Fri, Jan 30, 2004 at 11:46:31AM +1100, Neil Brown wrote:
>>
>>>On Sunday January 25, hanasaki@hanaden.com wrote:
>>>
>>>>The below is being reported, on and off, when hitting nfs-kernel-servers
>>>>running on 2.6.0 and 2.6.1 Could someone tell me if this is smoe bug or
>>>>what? Thanks
>>>> RPC request reserved 0 but used 124
>>>>
>>>>Debian sarge
>>>>nfs-kernel-server
>>>>am-untils
>>>>nfsv3 over tcp
>>>>
>>>
>>>stale file handles is a known bug that is fixed in the but BK and will
>>>be in 2.6.3.
>>
>>do you mean 2.6.2?
>
>
> Yeh, 2.6.2 as well.. But definitely 2.6.3 :-)
>
>
>>I've merged the nfsd stale file handles into 2.6.1-bk2 and it is working
>>fine on a nfs server here...
>
>
> good, thanks.
> NeilBrown
next prev parent reply other threads:[~2004-01-30 2:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4014675D.2040405@hanaden.com>
2004-01-30 0:46 ` [NFS] NFS rpc and stale handles on 2.6.x servers Neil Brown
2004-01-30 1:25 ` Mike Fedyk
2004-01-30 1:36 ` Neil Brown
2004-01-30 2:11 ` hanasaki [this message]
2004-01-30 11:55 ` Roman Kagan
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=4019BD48.60905@hanaden.com \
--to=hanasaki@hanaden.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
/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