From: Richard Laager <rlaager@wiktel.com>
To: Olga Kornievskaia <aglo@umich.edu>
Cc: NeilBrown <nfbrown@novell.com>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: PROBLEM: NFS Client Ignores TCP Resets
Date: Mon, 2 Oct 2017 19:09:53 -0500 [thread overview]
Message-ID: <20de1b7e-efca-e2e1-e9e0-e9aff5a1a1af@wiktel.com> (raw)
In-Reply-To: <CAN-5tyGc6jdJgSNio85wWXP1jEzjGmofmxpo3XhC9G+xc_NJPQ@mail.gmail.com>
On 10/02/2017 05:03 PM, Olga Kornievskaia wrote:
> On Mon, Oct 2, 2017 at 3:48 PM, Richard Laager <rlaager@wiktel.com> wrote:
>> On 10/02/2017 02:45 PM, Olga Kornievskaia wrote:
>>> Did turning off tcp checksum offloading take care of the problem by any chance?
>>
>> I don't think so, but I'm not 100% sure. I keep meaning to get back to
>> working on this, but since UDP is working and it's somewhat disruptive
>> to test, I haven't.
>
> From the network trace that you've provided shouldn't SEQ# should have
> been 545 instead of 465. If server is sending wrong values in the RST
> then client would drop it?
I don't know enough about TCP to be sure. But the RST has Ack: 465. I
think that's normal?
--
Richard
prev parent reply other threads:[~2017-10-03 0:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 2:24 PROBLEM: NFS Client Ignores TCP Resets Richard Laager
2016-03-08 17:06 ` Richard Laager
2016-03-09 21:16 ` Anna Schumaker
2016-03-09 21:42 ` Richard Laager
2016-03-11 9:44 ` Richard Laager
2016-04-02 1:43 ` Richard Laager
2016-04-03 3:58 ` NeilBrown
2016-04-07 9:45 ` Richard Laager
2016-04-08 0:47 ` NeilBrown
2017-10-02 19:29 ` Olga Kornievskaia
2017-10-02 22:13 ` NeilBrown
[not found] ` <CAN-5tyHuuBJxwqFLkiZa5ktBk7ypCJxmZ9creeD_RGWbK4Xn3A@mail.gmail.com>
2017-10-02 19:48 ` Richard Laager
2017-10-02 22:03 ` Olga Kornievskaia
2017-10-03 0:09 ` Richard Laager [this message]
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=20de1b7e-efca-e2e1-e9e0-e9aff5a1a1af@wiktel.com \
--to=rlaager@wiktel.com \
--cc=aglo@umich.edu \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nfbrown@novell.com \
--cc=trond.myklebust@primarydata.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 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.