On Thursday January 29, [email protected] wrote:
> On Fri, Jan 30, 2004 at 11:46:31AM +1100, Neil Brown wrote:
> > On Sunday January 25, [email protected] 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
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? http://www.kernel.org looks like its still on an RC2
of this.
Neil Brown wrote:
> On Thursday January 29, [email protected] wrote:
>
>>On Fri, Jan 30, 2004 at 11:46:31AM +1100, Neil Brown wrote:
>>
>>>On Sunday January 25, [email protected] 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