Subject: Re: 2.6.38.6 - state manager constantly respawns
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Harry Edmon <harry@uw.edu>
Cc: Chuck Lever <chuck.lever@oracle.com>, linux-nfs@vger.kernel.org
In-Reply-To: <4DD17CB5.7010009@uw.edu>
References: <4DD16FA8.4030602@uw.edu>
	 <05D08339-888C-4A64-BDC5-8667B3901E7A@oracle.com> <4DD1772E.9010609@uw.edu>
	 <6A6FB1C3-D4C3-40BE-810A-B4551FA9E591@oracle.com> <4DD17CB5.7010009@uw.edu>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 16 May 2011 15:43:27 -0400
Message-ID: <1305575007.19725.3.camel@lade.trondhjem.org>
Sender: linux-nfs-owner@vger.kernel.org
MIME-Version: 1.0

On Mon, 2011-05-16 at 12:36 -0700, Harry Edmon wrote:
> On 05/16/11 12:22, Chuck Lever wrote:
> > On May 16, 2011, at 3:12 PM, Harry Edmon wrote:
> >
> >    
> >> Attached is 1000 lines of output from tshark when the problem is occurring.   The client and server are connected by a private ethernet.
> >>      
> > Disappointing: tshark is not telling us the return codes.  However, I see "PUTFH;READ" then "RENEW" in a loop, which indicates the state manager thread is being kicked off because of ongoing difficulties with state recovery.  Is there a stuck application on that client?
> >
> > Try again with "tshark -V".
> >    
> Here is the output from tshark -V (first 50,000 lines).   Nothing 
> appears to be stuck, and as I said when I reboot the client into 2.6.32 
> the problem goes away, only to reappear when I reboot it back into 2.6.38.6.
> 

Possibly, but it definitely indicates a server bug. What kind of server
are you using?

Basically, the client is getting confused because when it sends a READ,
the server is telling it that the lease has expired, then when it sends
a RENEW, the same server replies that the lease is OK...

Trond
-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@netapp.com
www.netapp.com