From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: John Ronciak <john.ronciak@gmail.com>,
Grant Coady <gcoady.lk@gmail.com>,
linux-kernel@vger.kernel.org, neilb@suse.de,
bfields@fieldses.org, linux-nfs@vger.kernel.org,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Bruce Allan <bruce.w.allan@intel.com>,
PJ Waskiewicz <peter.p.waskiewicz.jr@intel.com>,
John Ronciak <john.ronciak@intel.com>,
e1000-devel@lists.sourceforge.net
Subject: Re: NFS regression? Odd delays and lockups accessing an NFS export.
Date: Sun, 24 Aug 2008 18:15:36 -0400 [thread overview]
Message-ID: <1219616136.14389.12.camel@localhost> (raw)
In-Reply-To: <1219615789.27921.152.camel@localhost.localdomain>
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.
Trond
next prev parent reply other threads:[~2008-08-24 22:15 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 2:02 NFS regression? Odd delays and lockups accessing an NFS export Grant Coady
2008-08-18 18:50 ` Athanasius
2008-08-18 19:19 ` Trond Myklebust
2008-08-18 19:37 ` J. K. Cliburn
2008-08-18 23:13 ` Athanasius
2009-05-12 20:27 ` Frank Filz
2009-05-13 0:05 ` Jay Cliburn
2008-08-18 19:20 ` Trond Myklebust
2008-08-20 1:10 ` Grant Coady
2008-08-20 23:17 ` Grant Coady
2008-08-22 10:23 ` Ian Campbell
2008-08-22 18:08 ` Trond Myklebust
2008-08-22 18:13 ` Ian Campbell
2008-08-22 19:33 ` John Ronciak
2008-08-22 20:00 ` Ian Campbell
2008-08-22 21:15 ` John Ronciak
2008-08-22 21:23 ` Trond Myklebust
2008-08-22 21:37 ` Ian Campbell
2008-08-22 21:56 ` Trond Myklebust
2008-08-22 22:41 ` Ian Campbell
2008-08-24 18:53 ` Ian Campbell
2008-08-24 19:17 ` Trond Myklebust
2008-08-24 19:19 ` Trond Myklebust
2008-08-24 22:09 ` Ian Campbell
2008-08-24 22:15 ` Trond Myklebust [this message]
2008-08-25 9:59 ` Ian Campbell
2008-08-25 16:04 ` Tom Tucker
2008-08-25 16:54 ` Trond Myklebust
2008-08-25 20:15 ` Tom Tucker
2008-08-26 19:27 ` J. Bruce Fields
2008-08-27 14:43 ` Tom Tucker
2008-08-30 15:47 ` Ian Campbell
2008-08-31 19:30 ` J. Bruce Fields
2008-08-31 19:44 ` Ian Campbell
2008-08-31 19:46 ` J. Bruce Fields
2008-08-31 19:49 ` Ian Campbell
2008-08-31 19:51 ` Tom Tucker
2008-08-31 19:51 ` Tom Tucker
2008-08-31 21:18 ` Ian Campbell
2008-09-01 17:20 ` Tom Tucker
2008-09-01 17:46 ` Ian Campbell
2008-09-10 8:40 ` Ian Campbell
2008-09-12 22:43 ` J. Bruce Fields
2008-09-12 23:15 ` Tom Tucker
2008-09-13 8:57 ` Ian Campbell
2008-09-16 5:48 ` Ian Campbell
2008-09-16 11:38 ` Tom Tucker
2008-09-16 15:03 ` Ian Campbell
2008-09-16 15:58 ` Tom Tucker
2008-09-16 16:24 ` Ian Campbell
2008-09-23 7:59 ` Ian Campbell
2008-09-23 11:33 ` Ian Campbell
2008-09-23 17:03 ` J. Bruce Fields
2008-09-26 15:37 ` Ian Campbell
2008-09-26 18:17 ` Ian Campbell
2008-09-27 3:54 ` J. Bruce Fields
2008-09-27 10:16 ` Ian Campbell
2008-08-25 21:39 ` Roger Heflin
2008-08-25 20:23 ` Grant Coady
2008-08-25 22:11 ` Trond Myklebust
2008-08-26 0:29 ` Grant Coady
2008-08-26 0:59 ` Muntz, Daniel
2008-08-26 1:06 ` Grant Coady
-- strict thread matches above, loose matches on Subject: below --
2008-09-10 2:51 Benoit Plessis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1219616136.14389.12.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=bfields@fieldses.org \
--cc=bruce.w.allan@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gcoady.lk@gmail.com \
--cc=ijc@hellion.org.uk \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@gmail.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=peter.p.waskiewicz.jr@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox