netdev
[Top] [All Lists]

Stale Filehandles was: [2.6] nfs_rename: target $file busy, d_count=2

To: Patrick Mau <mau@xxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
Subject: Stale Filehandles was: [2.6] nfs_rename: target $file busy, d_count=2
From: Mike Fedyk <mfedyk@xxxxxxxxxxxxx>
Date: Fri, 16 Jan 2004 10:55:04 -0800
In-reply-to: <20040116184031.GM1748@srv-lnx2600.matchmail.com>
Mail-followup-to: Patrick Mau <mau@xxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
References: <20040116050642.GF1748@srv-lnx2600.matchmail.com> <20040116130336.GA5220@oscar.prima.de> <20040116184031.GM1748@srv-lnx2600.matchmail.com>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.4i
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...

<Prev in Thread] Current Thread [Next in Thread>