From: Mike Javorski <mike.javorski@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: NFS server regression in kernel 5.13 (tested w/ 5.13.9)
Date: Sun, 8 Aug 2021 15:37:48 -0700 [thread overview]
Message-ID: <CAOv1SKCmdtchm5Z2NU80o49tkrHpAkPFaHKj4-vLDN5bZNCz-Q@mail.gmail.com> (raw)
I have been experiencing nfs file access hangs with multiple release
versions of the 5.13.x linux kernel. In each case, all file transfers
freeze for 5-10 seconds and then resume. This seems worse when reading
through many files sequentially.
My server:
- Archlinux w/ a distribution provided kernel package
- filesystems exported with "rw,sync,no_subtree_check,insecure" options
Client:
- Archlinux w/ latest distribution provided kernel (5.13.9-arch1-1 at writing)
- nfs mounted via /net autofs with "soft,nodev,nosuid" options
(ver=4.2 is indicated in mount)
I have tried the 5.13.x kernel several times since the first arch
release (most recently with 5.13.9-arch1-1), all with similar results.
Each time, I am forced to downgrade the linux package to a 5.12.x
kernel (5.12.15-arch1 as of writing) to clear up the transfer issues
and stabilize performance. No other changes are made between tests. I
have confirmed the freezing behavior using both ext4 and btrfs
filesystems exported from this server.
At this point I would appreciate some guidance in what to provide in
order to diagnose and resolve this issue. I don't have a lot of kernel
debugging experience, so instruction would be helpful.
- mike
next reply other threads:[~2021-08-08 22:38 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 22:37 Mike Javorski [this message]
2021-08-08 22:47 ` NFS server regression in kernel 5.13 (tested w/ 5.13.9) Chuck Lever III
2021-08-08 23:23 ` Mike Javorski
2021-08-09 0:01 ` NeilBrown
2021-08-09 0:28 ` Mike Javorski
2021-08-10 0:50 ` Mike Javorski
2021-08-10 1:28 ` NeilBrown
2021-08-10 11:54 ` Daire Byrne
2021-08-13 1:51 ` Mike Javorski
2021-08-13 2:39 ` NeilBrown
2021-08-13 2:53 ` Mike Javorski
2021-08-15 1:23 ` Mike Javorski
2021-08-16 1:20 ` NeilBrown
2021-08-16 13:21 ` Chuck Lever III
2021-08-16 16:25 ` Mike Javorski
2021-08-16 23:01 ` NeilBrown
2021-08-20 0:31 ` NeilBrown
2021-08-20 0:52 ` Mike Javorski
2021-08-22 0:17 ` Mike Javorski
2021-08-22 3:41 ` NeilBrown
2021-08-22 4:05 ` Mike Javorski
2021-08-22 22:00 ` NeilBrown
2021-08-26 19:34 ` Mike Javorski
2021-08-26 21:44 ` NeilBrown
2021-08-27 0:07 ` Mike Javorski
2021-08-27 5:27 ` NeilBrown
2021-08-27 6:11 ` Mike Javorski
2021-08-27 7:14 ` NeilBrown
2021-08-27 14:13 ` Chuck Lever III
2021-08-27 17:07 ` Mike Javorski
2021-08-27 22:00 ` Mike Javorski
2021-08-27 23:49 ` Chuck Lever III
2021-08-28 3:22 ` Mike Javorski
2021-08-28 18:23 ` Chuck Lever III
2021-08-29 22:36 ` [PATCH] SUNRPC: don't pause on incomplete allocation NeilBrown
2021-08-30 9:12 ` Mel Gorman
2021-08-30 20:46 ` J. Bruce Fields
[not found] ` <163027609524.7591.4987241695872857175@noble.neil.brown.name>
2021-08-30 9:11 ` [PATCH] MM: clarify effort used in alloc_pages_bulk_*() Mel Gorman
2021-09-04 17:41 ` NFS server regression in kernel 5.13 (tested w/ 5.13.9) Mike Javorski
2021-09-05 2:02 ` Chuck Lever III
2021-09-16 2:45 ` Mike Javorski
2021-09-16 18:58 ` Chuck Lever III
2021-09-16 19:21 ` Mike Javorski
2021-09-17 14:41 ` J. Bruce Fields
2021-08-16 16:09 ` Mike Javorski
2021-08-16 23:04 ` NeilBrown
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=CAOv1SKCmdtchm5Z2NU80o49tkrHpAkPFaHKj4-vLDN5bZNCz-Q@mail.gmail.com \
--to=mike.javorski@gmail.com \
--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 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).