From: Tom Tucker Subject: Re: NFS regression? Odd delays and lockups accessing an NFS export. Date: Mon, 25 Aug 2008 11:04:08 -0500 Message-ID: <48B2D7F8.5020206@opengridcomputing.com> References: <1219087258.7192.19.camel@localhost> <1219400624.18774.67.camel@zakaz.uk.xensource.com> <1219428489.6919.21.camel@localhost> <1219428818.27921.43.camel@localhost.localdomain> <56a8daef0808221233h68853587n6015ca7d809b17e1@mail.gmail.com> <1219435207.27921.51.camel@localhost.localdomain> <1219440202.9097.14.camel@localhost> <1219441041.27921.57.camel@localhost.localdomain> <1219442213.9097.25.camel@localhost> <1219603981.27921.145.camel@localhost.localdomain> <1219605422.14389.2.camel@localhost> <1219605596.14389.5.camel@localhost> <1219615789.27921.152.camel@localhost.localdomain> <1219616136.14389.12.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: Ian Campbell , John Ronciak , Grant Coady , linux-kernel@vger.kernel.org, neilb@suse.de, bfields@fieldses.org, linux-nfs@vger.kernel.org, Jeff Kirsher , Jesse Brandeburg , Bruce Allan , PJ Waskiewicz , John Ronciak , e1000-devel@lists.sourceforge.net To: Trond Myklebust Return-path: In-Reply-To: <1219616136.14389.12.camel@localhost> Sender: linux-kernel-owner@vger.kernel.org List-ID: Trond Myklebust wrote: > On Sun, 2008-08-24 at 23:09 +0100, Ian Campbell wrote: >> (added some quoting from previous mail to save replying twice) >> >> On Sun, 2008-08-24 at 15:19 -0400, Trond Myklebust wrote: >>> On Sun, 2008-08-24 at 15:17 -0400, Trond Myklebust wrote: >>>> >From the tcpdump, it looks as if the NFS server is failing to close the >>>> socket, when the client closes its side. You therefore end up getting >>>> stuck in the FIN_WAIT2 state (as netstat clearly shows above). >>>> >>>> Is the server keeping the client in this state for a very long >>>> period? >> Well, it had been around an hour and a half on this occasion. Next time >> it happens I can wait longer but I'm pretty sure I've come back from >> time away and it's been wedged for at least a day. How long would you >> expect it to remain in this state for? > > The server should ideally start to close the socket as soon as it > receives the FIN from the client. I'll have a look at the code. > I don't think it should matter how long the connection stays in FIN WAIT, the client should reconnect anyway. Since the client seems to be the variable, I would think it might be an issue with the client reconnect logic? That said, 2.6.25 is when the server side transport switch logic went in. Tom > Trond > > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html