From: Mike Fedyk <mfedyk@matchmail.com>
To: Patrick Mau <mau@oscar.ping.de>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: Stale Filehandles was: [2.6] nfs_rename: target $file busy, d_count=2
Date: Fri, 16 Jan 2004 12:16:23 -0800 [thread overview]
Message-ID: <20040116201623.GO1748@srv-lnx2600.matchmail.com> (raw)
In-Reply-To: <20040116185504.GN1748@srv-lnx2600.matchmail.com>
On Fri, Jan 16, 2004 at 10:55:04AM -0800, Mike Fedyk wrote:
> On Fri, Jan 16, 2004 at 10:40:31AM -0800, Mike Fedyk wrote:
> > I only had a few nfs clients doing light load, (kde home directories, and
> > such) and was able to reproduce stale nfs file handles just by running "find
> > > /dev/null" on the nfs share.
> >
> > Have you tried the -mm tree recently? 2.6.1-mm4 even has some new nfsd
> > patches in there (maybe you should wait until -mm5 though, there are a few
>
> Stale filehandles is the main problem right now, and I don't see how
> nfs_raname would be related (just that it was there while I was having
> trouble with the stale file handles...)
>
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm4/broken-out/nfsd-01-stale-filehandles-fixes.patch
>
> This one looks particularly interesting...
>
Most of the nfs client patches are for NFS4 or RPCSEC_GSS. Except for:
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm4/broken-out/
nfs-26-sock_disconnect.patch
nfs-31-attr.patch
nfs-client-deadlock-fix.patch
nfs-fix-bogus-setattr-calls.patch
nfs-open-intent-fix.patch
nfs-optimise-COMMIT-calls.patch
nfs-readonly-mounts-fix.patch
nfs-rpc-debug-oops-fix.patch
These might be interesting to test, but so far I haven't had troubles with
the stock Linus 2.6 nfs3 client.
Mike
next prev parent reply other threads:[~2004-01-16 20:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 5:06 Fwd: Re: [2.6] nfs_rename: target $file busy, d_count=2 Mike Fedyk
2004-01-16 13:03 ` Patrick Mau
2004-01-16 18:40 ` Mike Fedyk
2004-01-16 18:55 ` Stale Filehandles was: " Mike Fedyk
2004-01-16 20:16 ` Mike Fedyk [this message]
[not found] ` <20040117184716.GX1748@srv-lnx2600.matchmail.com>
2004-01-20 20:12 ` [SOLVED] " Mike Fedyk
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=20040116201623.GO1748@srv-lnx2600.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mau@oscar.ping.de \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).