From: Jason L Tibbitts III <tibbs@math.uh.edu>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: "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: Fri, 25 Jan 2019 13:51:30 -0600 [thread overview]
Message-ID: <ufak1isms71.fsf@epithumia.math.uh.edu> (raw)
In-Reply-To: <eff194a660ce562753d0112cdf6b1aacc5aa5dfb.camel@hammerspace.com> (Trond Myklebust's message of "Thu, 24 Jan 2019 19:58:40 +0000")
>>>>> "TM" == Trond Myklebust <trondmy@hammerspace.com> writes:
TM> Commit deaa5c96c2f7 ("SUNRPC: Address Kerberos performance/behavior
TM> regression") was supposed to be marked for stable as a fix.
I wonder, though; is that likely to be the root of the problem I'm
seeing? The commit description talks about this as a performance
regression, but I'm seeing a complete loss of NFS functionality.
Sadly I still don't have a reproducer, so outside of just deploying the
patch and hoping, I have no way to actually test this. So far I've been
running things like:
stress-ng --all 0 --class 'filesystem' -t 10m --times
in an NFS4-krb5p mounted directory without being able to reproduce the
problem. That drives the load up close to 200 but everything seems to make
progress. So it must be some specific sequence that causes it; I just
don't know which.
I did get this to show up in the kernel log, though, when I typed "df"
while running that stress-ng command was running:
[94547.656419] NFS: server nas00 error: fileid changed
fsid 0:57: expected fileid 0x6bc27eb, got 0x9996c6
I've never seen that one before, but it doesn't seem to hurt anything.
(This is still with 4.20.3.)
- J<
next prev parent reply other threads:[~2019-01-25 19:51 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 [this message]
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
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=ufak1isms71.fsf@epithumia.math.uh.edu \
--to=tibbs@math.uh.edu \
--cc=Anna.Schumaker@netapp.com \
--cc=Chuck.Lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@hammerspace.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 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).