Received-SPF: pass (google.com: domain of linux-nfs+bounces-2462-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
From: Benjamin Coddington <bcodding@redhat.com>
To: Roland Mainz <roland.mainz@nrubsig.org>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: "svc_tcp_read_marker nfsd RPC fragment too large" with Linux 6.6
 LTS nfsd ...
Date: Mon, 25 Mar 2024 08:21:28 -0400
Message-ID: <B119F413-D9A5-494A-8981-5FF1A493D99F@redhat.com>
In-Reply-To: <CAKAoaQng8vUV2uHNwNxhcL-d17ULPqO0iCSUmVKHunfSaHLMTg@mail.gmail.com>
References: <CAKAoaQng8vUV2uHNwNxhcL-d17ULPqO0iCSUmVKHunfSaHLMTg@mail.gmail.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain

On 22 Mar 2024, at 7:11, Roland Mainz wrote:

> Hi!
>
> ----
>
> After updating my Debian 11 and RHEL 9 installations with Linux kernel
> 6.6.20-rt25 I start getting the following error messages
> "svc_tcp_read_marker nfsd RPC fragment too large".
> Client side is Linux NFSv4.2 client (Debian&&RHEL, both default kernel
> and Linux 6.6.20-rt25)+ms-nfs41-client HEAD.
>
> Is this a know issue, and is there a patch for it ?


I could be mistaken, but isn't the server complaining that the client is
sending requests larger than ca_maxrequestsize?

Ben