From: Chuck Lever <chuck.lever@oracle.com>
To: "Aurélien Couderc" <aurelien.couderc2002@gmail.com>,
linux-nfs@vger.kernel.org
Subject: Re: READ_PLUS broken in Linux 6.12, worked in Linux 5.10! Re: [PATCH 1/1] DIO: add NFSv4.2 READ_PLUS support for nfstest_dio
Date: Thu, 30 Oct 2025 09:10:40 -0400 [thread overview]
Message-ID: <c2f48a2f-1934-466e-822e-b64a510b635a@oracle.com> (raw)
In-Reply-To: <CA+1jF5ovASc6zVHE7HA7MumKnpzvadGw_vyjV+ELttxv5tCCTQ@mail.gmail.com>
On 10/30/25 6:54 AM, Aurélien Couderc wrote:
> On Thu, Oct 2, 2025 at 10:22 AM Aurélien Couderc
> <aurelien.couderc2002@gmail.com> wrote:
>>
>> On Thu, Oct 2, 2025 at 12:29 AM Dai Ngo <dai.ngo@oracle.com> wrote:
>>>
>>> From: Oracle Public Cloud User <opc@dngo-nfstest-client.allregionaliads.osdevelopmeniad.oraclevcn.com>
>>>
>>> Check for nfs_version >= 4.2 and use READ_PLUS instead of READ.
>>
>> FYI READ_PLUS is **BROKEN** for sparse files. It was working in Linux
>> 5.10, but as soon as we switched to Linux 6.12 it reported only data
>> and no holes in sparse files. We're back to Linux 5.10 and cannot
>> upgrade because of this.
>
> Is there any bug tracker where I can post this Linux NFS server bug?
https://bugzilla.kernel.org, Product "File Systems", Component "NFSD"
--
Chuck Lever
prev parent reply other threads:[~2025-10-30 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 22:28 [PATCH 1/1] DIO: add NFSv4.2 READ_PLUS support for nfstest_dio Dai Ngo
2025-10-01 23:53 ` Trond Myklebust
2025-10-02 4:00 ` Dai Ngo
2025-10-02 8:25 ` pahtconf() api to test for sparse file support? " Aurélien Couderc
2025-10-02 8:22 ` READ_PLUS broken in Linux 6.12, worked in Linux 5.10! " Aurélien Couderc
2025-10-30 10:54 ` Aurélien Couderc
2025-10-30 13:10 ` Chuck Lever [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=c2f48a2f-1934-466e-822e-b64a510b635a@oracle.com \
--to=chuck.lever@oracle.com \
--cc=aurelien.couderc2002@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).