From: Reindl Harald <h.reindl@thelounge.net>
To: yukuai@fnnas.com, Thorsten Leemhuis <regressions@leemhuis.info>,
Jens Axboe <axboe@kernel.dk>
Cc: bugreports61@gmail.com, linux-raid@vger.kernel.org,
linan122@huawei.com, xni@redhat.com, regressions@lists.linux.dev,
Linus Torvalds <torvalds@linux-foundation.org>,
Paul Menzel <pmenzel@molgen.mpg.de>, Song Liu <song@kernel.org>
Subject: Re: Issues with md raid 1 on kernel 6.18 after booting kernel 6.19-rc1 once
Date: Wed, 17 Dec 2025 14:50:50 +0100 [thread overview]
Message-ID: <98e0403a-806e-44a2-9420-e19092bb5206@thelounge.net> (raw)
In-Reply-To: <0f44559f-7732-4506-922f-04a244d54c35@fnnas.com>
Am 17.12.25 um 14:45 schrieb Yu Kuai:
> AFAIK, possible options:
> 1) always set lbs for arrays for new kernel, and backport the patch for
> old kernels so that users can still assemble the array.(current option)
> 2) only set lbs by default for new array, for assembling the array still
> left the lbs field unset, in this case the data loss problem is not fixed,
> we should also print a warning and guide users to set lbs to fix the problem,
> with the notification the array will not be assembled in old kernels.
> 3) revert the new feature to set lbs for mdraids
option 2 including the guide so that everybody can decide "i am fine now
never boot a older kernel" and activate it
how it's done now you burn possible testers of new kernels in the future
when bitten once
next prev parent reply other threads:[~2025-12-17 13:51 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
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 [this message]
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=98e0403a-806e-44a2-9420-e19092bb5206@thelounge.net \
--to=h.reindl@thelounge.net \
--cc=axboe@kernel.dk \
--cc=bugreports61@gmail.com \
--cc=linan122@huawei.com \
--cc=linux-raid@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=song@kernel.org \
--cc=torvalds@linux-foundation.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.