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

[hanasaki]

I have been having them consistently with 2.6.0 and 2.6.1 clients 
against 2.6.0 and/or 2.6.1 servers.

2.6.1 and 2.6.0 against a 2.4.x server has no problems.

Jonathan Boler 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...
>
>
> I was getting alot of nfsv3 stale file handles with 2.6.1-mm1 so I dropped back to 2.6.1.
>
> mm5 seems to have fixed everything.
>
> Jonathan
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/