From: Trond Myklebust <trondmy@hammerspace.com>
To: "tibbs@math.uh.edu" <tibbs@math.uh.edu>
Cc: "bcodding@redhat.com" <bcodding@redhat.com>,
"Anna.Schumaker@netapp.com" <Anna.Schumaker@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"Chuck.Lever@oracle.com" <Chuck.Lever@oracle.com>
Subject: Re: Need help debugging NFS issues new to 4.20 kernel
Date: Wed, 20 Feb 2019 16:45:52 +0000 [thread overview]
Message-ID: <ef322de97094192e97bc897c5a9f41687720e076.camel@hammerspace.com> (raw)
In-Reply-To: <ufalg2abf6n.fsf@epithumia.math.uh.edu>
On Wed, 2019-02-20 at 10:25 -0600, Jason L Tibbitts III wrote:
> > > > > > "TM" == Trond Myklebust <trondmy@hammerspace.com> writes:
>
> TM> This is not an RPC layer issue. It is a SEQ_MISORDERED error on
> slot
> TM> 0. If the client can't recover then that will hang your NFSv4.1
> TM> session against that server.
>
> TM> Are you sure this isn't what was happening previously?
>
> I'm sorry if I wasn't clear. I applied your patch and it doesn't
> seem
> to make any difference. The behavior appears to be exactly what was
> happening previously, though I posted the trace again just so that
> those
> who know more than me could verify that.
>
That's why I sent you a patch that addresses the SEQ_MISORDERED issue.
Are you saying that failed too?
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2019-02-20 16:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 17:32 Need help debugging NFS issues new to 4.20 kernel Jason L Tibbitts III
2019-01-24 19:28 ` Jason L Tibbitts III
2019-01-24 19:58 ` Trond Myklebust
2019-01-25 19:13 ` Schumaker, Anna
2019-01-26 17:59 ` Sasha Levin
2019-01-25 19:51 ` Jason L Tibbitts III
2019-02-05 18:12 ` Jason Tibbitts
2019-02-06 12:05 ` Benjamin Coddington
[not found] ` <87imxwab12.fsf@hippogriff.math.uh.edu>
2019-02-07 11:13 ` Benjamin Coddington
[not found] ` <87d0o3aadg.fsf@hippogriff.math.uh.edu>
2019-02-08 12:01 ` Benjamin Coddington
2019-02-08 15:19 ` Chuck Lever
2019-02-08 17:17 ` Jason L Tibbitts III
2019-02-15 20:33 ` Jason L Tibbitts III
2019-02-16 14:46 ` Trond Myklebust
2019-02-20 2:13 ` Jason L Tibbitts III
2019-02-20 15:25 ` Jason L Tibbitts III
2019-02-20 15:37 ` Trond Myklebust
2019-02-20 15:39 ` Chuck Lever
2019-02-20 15:41 ` Trond Myklebust
2019-02-21 18:19 ` Jason L Tibbitts III
2019-02-25 19:24 ` Jason L Tibbitts III
2019-02-25 23:15 ` Benjamin Coddington
2019-02-20 16:25 ` Jason L Tibbitts III
2019-02-20 16:45 ` Trond Myklebust [this message]
2019-02-20 16:49 ` Jason L Tibbitts III
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=ef322de97094192e97bc897c5a9f41687720e076.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=Anna.Schumaker@netapp.com \
--cc=Chuck.Lever@oracle.com \
--cc=bcodding@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=tibbs@math.uh.edu \
/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.