From: Benjamin Coddington <ben.coddington@hammerspace.com>
To: Rik Theys <Rik.Theys@esat.kuleuven.be>
Cc: Linux Nfs <linux-nfs@vger.kernel.org>
Subject: Re: NFS4ERR_SEQ_MISORDERED errors and NFS client very slow
Date: Thu, 30 Apr 2026 09:27:55 -0400 [thread overview]
Message-ID: <CB5BA5C0-15AA-49D0-96B9-2017F6617903@hammerspace.com> (raw)
In-Reply-To: <2cb85a89-f896-4504-b1cf-e4494d344ffe@esat.kuleuven.be>
On 30 Apr 2026, at 2:53, Rik Theys wrote:
> Hi,
>
> We have a Rocky 8 client running Linux 7.0.2 (kernel-ml from elrepo) that is an NFS client to a RHEL10 server.
>
> Lately we've noticed that NFS performance is very poor for certain workloads (We saw the same issue on the stock EL8 kernel, 6.18.20 and now 7.0.2). For example cloning git repositories is extremely slow.
>
> Looking at the server side there don't seem to be any saturations of the disk or network subsystems.
>
> I've taken a network dump between the client and server. In that dump I see that the server frequently responds to requests from the client with NFS4ERR_SEQ_MISORDERED (10063). What could be the cause of these mismatches? Is this always a client issue, or can this be caused by the server?
This is something you shouldn't normally see and probably indicates a bug or
serious problem. From the client side you'd only expect this if you're
doing a lot of task signaling so that the userland processes abandon RPCs.
A packet capture is the best way to determine if the server is mis-reporting
the sequencing problem, or if the client's sequencing is incorrect. Given
your description of the symptoms I'd also check to make sure your underlying
network isn't doing something totally nuts like duplicating packets.
Ben
next prev parent reply other threads:[~2026-04-30 13:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 6:53 NFS4ERR_SEQ_MISORDERED errors and NFS client very slow Rik Theys
2026-04-30 13:27 ` Benjamin Coddington [this message]
2026-04-30 14:26 ` Rik Theys
2026-04-30 14:34 ` Rick Macklem
2026-04-30 14:39 ` Rick Macklem
2026-04-30 15:03 ` Rik Theys
2026-04-30 15:02 ` Rick Macklem
2026-04-30 15:27 ` Rik Theys
2026-04-30 15:35 ` Rick Macklem
2026-04-30 16:24 ` Rick Macklem
2026-04-30 17:04 ` Rik Theys
2026-04-30 17:29 ` Olga Kornievskaia
2026-04-30 18:08 ` Rik Theys
2026-04-30 18:28 ` Olga Kornievskaia
2026-05-04 7:30 ` Rik Theys
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=CB5BA5C0-15AA-49D0-96B9-2017F6617903@hammerspace.com \
--to=ben.coddington@hammerspace.com \
--cc=Rik.Theys@esat.kuleuven.be \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).