From: BugReports <bugreports61@gmail.com>
To: yukuai@fnnas.com, linux-raid@vger.kernel.org,
linan122@huawei.com, xni@redhat.com
Subject: Re: Issues with md raid 1 on kernel 6.18 after booting kernel 6.19rc1 once
Date: Wed, 17 Dec 2025 08:25:24 +0100 [thread overview]
Message-ID: <2d9aa651-93b6-407c-b7a1-092e454134bf@gmail.com> (raw)
In-Reply-To: <f20c3a92-d562-4ac2-98b6-39ff4f3e3bbf@fnnas.com>
Hi,
many thx for the clarification cause that makes a huge diff !
Br
Am 17.12.25 um 08:17 schrieb Yu Kuai:
> Hi,
>
> 在 2025/12/17 15:13, BugReports 写道:
>> ...
>>
>> We'll have to backport following patch into old kernels to make new
>> arrays to assemble in old
>> kernels.
>>
>> ....
>>
>>
>> The md array which i am talking about was not created with kernel
>> 6.19, it was created sometime in 2024.
>>
>> It was just used in kernel 6.19 and that broke compatibility with my
>> 6.18 kernel.
> I know, I mean any array that is created or assembled in new kernels will now have
> lsb field stored in metadata. This field is not defined in old kernels and that's why
> array can't assembled in old kernels, due to unknown metadata.
>
> This is what we have to do for new features, and we're planning to avoid the forward
> compatibility issue with the above patch that I mentioned.
>
next prev parent reply other threads:[~2025-12-17 7:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 6:58 Issues with md raid 1 on kernel 6.18 after booting kernel 6.19rc1 once BugReports
2025-12-17 7:06 ` Yu Kuai
2025-12-17 7:13 ` BugReports
2025-12-17 7:17 ` Yu Kuai
2025-12-17 7:25 ` BugReports [this message]
2025-12-17 7:33 ` Issues with md raid 1 on kernel 6.18 after booting kernel 6.19-rc1 once Paul Menzel
2025-12-17 7:41 ` Yu Kuai
2025-12-17 8:02 ` Reindl Harald
2025-12-17 8:33 ` Yu Kuai
2025-12-17 13:07 ` Thorsten Leemhuis
2025-12-17 13:45 ` Yu Kuai
2025-12-17 13:50 ` Reindl Harald
2025-12-17 13:24 ` Issues with md raid 1 on kernel 6.18 after booting kernel 6.19rc1 once Li Nan
2025-12-18 10:41 ` Bugreports61
2025-12-18 14:54 ` Li Nan
2025-12-18 16:04 ` BugReports
2025-12-19 8:22 ` Li Nan
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=2d9aa651-93b6-407c-b7a1-092e454134bf@gmail.com \
--to=bugreports61@gmail.com \
--cc=linan122@huawei.com \
--cc=linux-raid@vger.kernel.org \
--cc=xni@redhat.com \
--cc=yukuai@fnnas.com \
/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.