From: Emmanuel Florac <eflorac@intellique.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Hard to debug NFS loss of connectivity
Date: Fri, 6 Sep 2013 18:55:08 +0200 [thread overview]
Message-ID: <20130906185508.3f0d2730@harpe.intellique.com> (raw)
In-Reply-To: <20130906160735.GA16396@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
Le Fri, 6 Sep 2013 12:07:35 -0400
"J. Bruce Fields" <bfields@fieldses.org> écrivait:
> Weird. Things look normal up through frame 14, which is a READDIRPLUS
> reply. Then the server resends the reply after .2s, and and the
> client resends its call shortly thereafter (but without acking the
> latest reply). And then the rest of the trace is resends of the
> reply.
>
> So it looks like the client stopped ACKing the server's replies?
>
> You may also have filtered out some TCP ACKs, which makes this harder
> to work out.
Ah yes, my bad, one TCP ACK was filtered out. Here I've kept trafic
between the two machines but ssh.
Here I was capturing from the server, maybe I should try capturing on
the client side?
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
[-- Attachment #2: nfserror2.pcap --]
[-- Type: application/vnd.tcpdump.pcap, Size: 2280 bytes --]
next prev parent reply other threads:[~2013-09-06 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 17:18 Hard to debug NFS loss of connectivity Emmanuel Florac
2013-09-05 20:45 ` J. Bruce Fields
2013-09-05 21:34 ` Emmanuel Florac
2013-09-05 21:40 ` J. Bruce Fields
2013-09-06 15:57 ` Emmanuel Florac
2013-09-06 16:07 ` J. Bruce Fields
2013-09-06 16:55 ` Emmanuel Florac [this message]
2013-09-10 13:28 ` J. Bruce Fields
2013-09-10 13:34 ` Emmanuel Florac
2013-09-06 17:15 ` Jim Rees
2013-09-11 15:11 ` Hard to debug NFS loss of connectivity: problem solved Emmanuel Florac
2013-09-11 20:14 ` 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=20130906185508.3f0d2730@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.