From: Trond Myklebust <trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
To: Linux Network Devel Mailing List
<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux NFS Mailing List
<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Weird TCP hang when doing loopback NFS (wireshark traces attached)
Date: Sun, 01 Mar 2015 14:14:51 -0500 [thread overview]
Message-ID: <1425237291.24845.13.camel@primarydata.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
Hi,
When doing testing of NFSv3 loopback mounts (client and server are on
the same IP address), I'm seeing a very reproducible hang in which the
client stops receiving data from the server. The TCP connection is still
marked as established, and the server appears to continue to receive and
send data, however the client does not.
So far, I've reproduced on both v4.0-rc1, and the Fedora v3.18.7 kernel.
The reproducer is simply to loopback mount using NFSv3, and then run the
'fsx' filesystem exerciser. I'm usually able to trigger the hang with
"fsx -N 100000 foobar".
I've attached a couple of wireshark trace of a few frames just before
and during the hang in case it jogs any memories.
Cheers
Trond
[-- Attachment #2: dump_lastframes.out.pcapng.gz --]
[-- Type: application/x-pcapng, Size: 1689 bytes --]
[-- Attachment #3: dump_3.18.7_lastframes.pcapng.gz --]
[-- Type: application/x-pcapng, Size: 49636 bytes --]
next reply other threads:[~2015-03-01 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 19:14 Trond Myklebust [this message]
[not found] ` <1425237291.24845.13.camel-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
2015-03-02 0:52 ` Weird TCP hang when doing loopback NFS (wireshark traces attached) Trond Myklebust
2015-03-02 1:06 ` Bruce James Fields
2015-03-02 1:20 ` Trond Myklebust
2015-03-02 4:31 ` Trond Myklebust
[not found] ` <CAHQdGtQnbPWYhdvwTGJKUD4mt8x_rmQjCH3AO4X17Y4RBSpUQQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-02 19:58 ` Bruce James 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=1425237291.24845.13.camel@primarydata.com \
--to=trond.myklebust-7i+n7zu2hftekmmhf/gkza@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).