From: "Mantas Mikulėnas" <grawity@gmail.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Data corruption with 5.10.x client -> 6.5.x server
Date: Tue, 26 Sep 2023 07:41:29 +0300 [thread overview]
Message-ID: <8cb19861-7fd2-4d12-bd76-78bbb8fcee7c@gmail.com> (raw)
In-Reply-To: <CA1D7203-72FB-4681-AD60-F1D80A57C154@oracle.com>
On 25/09/2023 22.22, Chuck Lever III wrote:
>> On Sep 24, 2023, at 2:24 PM, Chuck Lever III <chuck.lever@oracle.com> wrote:
>>
>>> On Sep 24, 2023, at 12:51 PM, Mantas Mikulėnas <grawity@gmail.com> wrote:
>>>
>>> Right, whereas on the server, the first file is filled with "Hello World (4092 bytes)" as I originally tried to narrow down the issue.
>>>
>>> Meanwhile, 6.4.x (Arch) clients don't seem to be having any problems with the same server, and with seemingly the same mount options.
>>>
>>> Thanks for looking into it!<nfs_krb5i_working_6.4client.pcap>
>> I found /a/ problem with the nfsd-fixes branch and krb5i, but
>> maybe not /your/ problem, and it's with a recent client. Scrounging
>> a v5.10-vintage client is a little more work, we'll see if that's
>> needed for confirming an eventual fix.
> The issue I reproduced appears to be unrelated.
>
> I'm wondering if I can get you to bisect the server kernel using
> your v5.10 client to test? good = v6.4, bad = v6.5 should do it.
Yeah, I will try to bisect but it'll probably take a day or two.
next prev parent reply other threads:[~2023-09-26 4:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 13:07 Data corruption with 5.10.x client -> 6.5.x server Mantas Mikulėnas
2023-09-24 13:28 ` Chuck Lever III
2023-09-24 14:32 ` Mantas Mikulėnas
2023-09-24 14:44 ` Chuck Lever III
2023-09-24 16:51 ` Mantas Mikulėnas
2023-09-24 18:24 ` Chuck Lever III
2023-09-25 19:22 ` Chuck Lever III
2023-09-26 4:41 ` Mantas Mikulėnas [this message]
2023-09-26 13:57 ` Chuck Lever III
2023-09-26 21:52 ` Olga Kornievskaia
2023-09-26 22:55 ` Chuck Lever III
2023-09-27 8:45 ` Mantas Mikulėnas
2023-09-27 9:41 ` Mantas Mikulėnas
2023-09-27 13:08 ` Chuck Lever III
2023-09-27 13:30 ` Linux regression tracking #adding (Thorsten Leemhuis)
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=8cb19861-7fd2-4d12-bd76-78bbb8fcee7c@gmail.com \
--to=grawity@gmail.com \
--cc=chuck.lever@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.