From: Ian Campbell <ijc@hellion.org.uk>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-nfs@vger.kernel.org, Max Kellermann <mk@cm4all.com>,
linux-kernel@vger.kernel.org, gcosta@redhat.com,
Grant Coady <grant_lkml@dodo.com.au>,
"J. Bruce Fields" <bfields@fieldses.org>,
Tom Tucker <tom@opengridcomputing.com>
Subject: Re: [PATCH] NFS regression in 2.6.26?, "task blocked for more than 120 seconds"
Date: Wed, 26 Nov 2008 22:12:19 +0000 [thread overview]
Message-ID: <1227737539.31008.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1227621877.9425.102.camel@zakaz.uk.xensource.com>
[-- Attachment #1: Type: text/plain, Size: 5264 bytes --]
On Tue, 2008-11-25 at 14:04 +0000, Ian Campbell wrote:
> On Tue, 2008-11-25 at 08:57 -0500, Trond Myklebust wrote:
> > On Tue, 2008-11-25 at 13:38 +0000, Ian Campbell wrote:
> > > > That would indicate that the server is failing to close the TCP
> > > > connection when the client closes on its end.
> > > >
> > > > Could you remind me what server you are using?
> > >
> > > 2.6.25-2-486 which is a Debian package from backports.org, changelog
> > > indicates that it contains 2.6.25.7.
> >
> > Hmm... It should normally close sockets when the state changes. There
> > might be a race, though...
> >
> > > > Also, does 'netstat -t'
> > > > show connections that are stuck in the CLOSE_WAIT state when you see the
> > > > hang?
> > >
> > > I'd have to wait for it to reproduce again to be 100% sure but according
> > > to http://lkml.indiana.edu/hypermail/linux/kernel/0808.3/0120.html
> > > I was seeing connections in FIN_WAIT2 but not CLOSE_WAIT.
> >
> > That would be on the client side. I'm talking about the server.
>
> Ah, OK. I'll abort my current test of 2.6.26+revert and wait for a repro
> so I can netstat the server, give me a couple of days...
So on the server I see the following. 192.168.1.4 is the problematic
client and 192.168.1.6 is the server.
Maybe not interesting but 192.168.1.5 also uses NFS for my $HOME and
runs 2.6.26 with no lockups.
# netstat -t -n
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 1 0 192.168.1.6:2049 192.168.1.4:723 CLOSE_WAIT
tcp 1 0 192.168.1.6:2049 192.168.1.4:920 CLOSE_WAIT
tcp 1 0 192.168.1.6:2049 192.168.1.4:890 CLOSE_WAIT
tcp 1 0 192.168.1.6:2049 192.168.1.4:698 CLOSE_WAIT
tcp 1 0 192.168.1.6:2049 192.168.1.4:705 CLOSE_WAIT
tcp 1 0 192.168.1.6:2049 192.168.1.4:943 CLOSE_WAIT
tcp 1 0 192.168.1.6:2049 192.168.1.4:915 CLOSE_WAIT
tcp 0 0 192.168.1.6:2049 192.168.1.5:783 ESTABLISHED
tcp 1 0 192.168.1.6:2049 192.168.1.4:998 CLOSE_WAIT
tcp 1 0 192.168.1.6:2049 192.168.1.4:758 CLOSE_WAIT
tcp 1 0 192.168.1.6:2049 192.168.1.4:955 CLOSE_WAIT
tcp 1 0 192.168.1.6:2049 192.168.1.4:845 CLOSE_WAIT
tcp 1 0 192.168.1.6:2049 192.168.1.4:827 CLOSE_WAIT
tcp 0 0 192.168.1.6:58464 128.31.0.36:80 ESTABLISHED
tcp 1 0 192.168.1.6:2049 192.168.1.4:754 CLOSE_WAIT
tcp 1 0 192.168.1.6:2049 192.168.1.4:837 CLOSE_WAIT
tcp 1 0 192.168.1.6:2049 192.168.1.4:918 CLOSE_WAIT
tcp 1 0 192.168.1.6:2049 192.168.1.4:865 CLOSE_WAIT
tcp 0 0 192.168.1.6:48343 192.168.1.5:832 ESTABLISHED
tcp 1 0 192.168.1.6:2049 192.168.1.4:840 CLOSE_WAIT
tcp 1 0 192.168.1.6:2049 192.168.1.4:883 CLOSE_WAIT
tcp 1 0 192.168.1.6:2049 192.168.1.4:785 CLOSE_WAIT
tcp 1 0 192.168.1.6:2049 192.168.1.4:720 CLOSE_WAIT
tcp6 0 0 ::ffff:192.168.1.6:22 ::ffff:192.168.1.:38206 ESTABLISHED
tcp6 0 0 ::ffff:192.168.1.6:143 ::ffff:192.168.1.:41308 ESTABLISHED
tcp6 0 0 ::ffff:192.168.1.6:143 ::ffff:192.168.1.:55784 ESTABLISHED
tcp6 0 0 ::ffff:192.168.1.6:22 ::ffff:192.168.1.:39046 ESTABLISHED
and on the client
# netstat -t -n
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 192.168.1.4:943 192.168.1.6:2049 FIN_WAIT2
tcp 0 0 192.168.1.4:33959 192.168.1.4:6543 ESTABLISHED
tcp 0 0 192.168.1.4:6543 192.168.1.4:54157 ESTABLISHED
tcp 0 0 127.0.0.1:13666 127.0.0.1:33364 ESTABLISHED
tcp 0 0 192.168.1.4:22 192.168.1.5:54696 ESTABLISHED
tcp 0 0 192.168.1.4:22 192.168.1.5:47599 ESTABLISHED
tcp 0 0 192.168.1.4:54156 192.168.1.4:6543 ESTABLISHED
tcp 0 0 192.168.1.4:6543 192.168.1.4:33957 ESTABLISHED
tcp 0 0 192.168.1.4:33957 192.168.1.4:6543 ESTABLISHED
tcp 0 0 192.168.1.4:54157 192.168.1.4:6543 ESTABLISHED
tcp 0 0 192.168.1.4:6543 192.168.1.4:54156 ESTABLISHED
tcp 0 0 192.168.1.4:6543 192.168.1.4:33959 ESTABLISHED
tcp 0 0 127.0.0.1:47756 127.0.0.1:6545 ESTABLISHED
tcp 0 0 127.0.0.1:33364 127.0.0.1:13666 ESTABLISHED
tcp 0 0 127.0.0.1:6545 127.0.0.1:47756 ESTABLISHED
>
> Ian.
--
Ian Campbell
Just once, I wish we would encounter an alien menace that wasn't
immune to bullets.
-- The Brigadier, "Dr. Who"
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-11-26 22:12 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 12:32 Max Kellermann
2008-10-17 14:33 ` Glauber Costa
2008-10-20 6:51 ` Max Kellermann
2008-10-20 7:43 ` Ian Campbell
2008-10-20 13:15 ` Glauber Costa
2008-10-20 14:12 ` Max Kellermann
2008-10-20 14:34 ` Cyrill Gorcunov
2008-10-20 14:21 ` Cyrill Gorcunov
2009-05-22 20:59 ` H. Peter Anvin
2009-05-25 13:12 ` Max Kellermann
2008-10-20 6:27 ` Ian Campbell
2008-11-01 11:45 ` Ian Campbell
2008-11-01 13:41 ` Trond Myklebust
2008-11-02 14:40 ` Ian Campbell
2008-11-07 2:12 ` kenneth johansson
2008-11-04 19:10 ` Ian Campbell
2008-11-25 7:09 ` Ian Campbell
2008-11-25 13:28 ` Trond Myklebust
2008-11-25 13:38 ` Ian Campbell
2008-11-25 13:57 ` Trond Myklebust
2008-11-25 14:04 ` Ian Campbell
2008-11-26 22:12 ` Ian Campbell [this message]
2008-12-01 0:17 ` [PATCH 0/3] " Trond Myklebust
2008-12-01 0:18 ` [PATCH 1/3] SUNRPC: Ensure the server closes sockets in a timely fashion Trond Myklebust
2008-12-17 15:27 ` Tom Tucker
2008-12-17 18:08 ` Trond Myklebust
2008-12-17 18:59 ` Tom Tucker
2008-12-01 0:19 ` [PATCH 2/3] SUNRPC: We only need to call svc_delete_xprt() once Trond Myklebust
2008-12-01 0:20 ` [PATCH 3/3] SUNRPC: svc_xprt_enqueue should not refuse to enqueue 'XPT_DEAD' transports Trond Myklebust
2008-12-17 15:35 ` Tom Tucker
2008-12-17 19:07 ` Trond Myklebust
2008-12-23 14:49 ` Tom Tucker
2008-12-23 23:39 ` Tom Tucker
2008-12-01 0:29 ` [PATCH 0/3] NFS regression in 2.6.26?, "task blocked for more than 120 seconds" Trond Myklebust
2008-12-02 15:22 ` Kasparek Tomas
2008-12-02 15:37 ` Trond Myklebust
2008-12-02 16:26 ` Kasparek Tomas
2008-12-02 18:10 ` Trond Myklebust
2008-12-01 22:09 ` Ian Campbell
2008-12-06 12:16 ` Ian Campbell
2008-12-14 18:24 ` Ian Campbell
2008-12-16 17:55 ` J. Bruce Fields
2008-12-16 18:39 ` Ian Campbell
2009-01-07 22:21 ` J. Bruce Fields
2009-01-08 18:20 ` J. Bruce Fields
2009-01-08 21:22 ` Ian Campbell
2009-01-08 21:26 ` J. Bruce Fields
2009-01-12 9:46 ` Ian Campbell
2009-01-22 8:27 ` Ian Campbell
2009-01-22 16:44 ` J. Bruce Fields
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=1227737539.31008.2.camel@localhost.localdomain \
--to=ijc@hellion.org.uk \
--cc=bfields@fieldses.org \
--cc=gcosta@redhat.com \
--cc=grant_lkml@dodo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mk@cm4all.com \
--cc=tom@opengridcomputing.com \
--cc=trond.myklebust@fys.uio.no \
/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
all inboxes | Powered by JetHome®