From: Rik Theys <Rik.Theys@esat.kuleuven.be>
To: Olga Kornievskaia <aglo@umich.edu>
Cc: Linux Nfs <linux-nfs@vger.kernel.org>
Subject: Re: NFS4ERR_SEQ_MISORDERED errors and NFS client very slow
Date: Mon, 4 May 2026 09:30:11 +0200 [thread overview]
Message-ID: <1835f2f9-b21e-413b-acd4-a2b69d96627c@esat.kuleuven.be> (raw)
In-Reply-To: <CAN-5tyGhC8q=iB_H6JaFZpwpWAqEz5NObVrzZ8m=3OzgLgJnpw@mail.gmail.com>
Hi,
On 4/30/26 7:29 PM, Olga Kornievskaia wrote:
> On Thu, Apr 30, 2026 at 2:54 AM Rik Theys <Rik.Theys@esat.kuleuven.be> 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 might have been fixed by mentioned patch below. This patch will
> be included in RHEL10.2 release.
>
> If you have the ability to change the kernel on your NFS server I
> would suggest trying some upstream version that has this patch
> included to see if the problem goes away or wait until when RHEL10.2
> comes out and test it.
We're now running 7.0.3 on the server. We will monitor if the
performance issue returns.
Thanks everybody for your time and effort.
Regards,
Rik
--
Rik Theys
System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark Arenberg 10 bus 2440 - B-3001 Leuven-Heverlee
+32(0)16/32.11.07
----------------------------------------------------------------
<<Any errors in spelling, tact or fact are transmission errors>>
prev parent reply other threads:[~2026-05-04 7:30 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
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 [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=1835f2f9-b21e-413b-acd4-a2b69d96627c@esat.kuleuven.be \
--to=rik.theys@esat.kuleuven.be \
--cc=aglo@umich.edu \
--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).