From: Li Nan <linan666@huaweicloud.com>
To: "Sven Köhler" <sven.koehler@gmail.com>,
"Li Nan" <linan666@huaweicloud.com>,
linux-raid@vger.kernel.org
Subject: Re: regression: drive was detected as raid member due to metadata on partition
Date: Thu, 18 Apr 2024 15:31:11 +0800 [thread overview]
Message-ID: <cffea7de-edf4-c97b-3fc7-c87038123593@huaweicloud.com> (raw)
In-Reply-To: <5a4a9b82-2082-4d25-906d-ee01b10fad65@gmail.com>
在 2024/4/14 5:37, Sven Köhler 写道:
[...]
>>
>> I used your command and config, updated kernel and mdadm, but raid also
>> created correctly after reboot.
>>
>> My OS is fedora, it may have been affected by some other system tools? I
>> have no idea.
>
> The Arch kernel has RAID autodetection enabled. I just tried to reproduce
> it. While mdadm will not consider /dev/sd[ab] as members, the kernel's
> autodetection will. For that you have to reboot.
>
It is not about autodetection. Autodetection only deals with the devices in
list 'all_detected_devices', device is added to it by blk_add_partition().
So sdx will not be added to this list, and will not be autodetect.
> I used this ISO in a VM with 2 harddisks to reproduce the issue:
> https://mirror.informatik.tu-freiberg.de/arch/iso/2024.04.01/archlinux-2024.04.01-x86_64.iso
>
>
>
> Kind Regards,
> Sven
>
>
> .
--
Thanks,
Nan
next prev parent reply other threads:[~2024-04-18 7:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 23:31 regression: drive was detected as raid member due to metadata on partition Sven Köhler
2024-04-10 1:56 ` Li Nan
2024-04-10 20:59 ` Sven Köhler
2024-04-11 2:25 ` Li Nan
2024-04-13 21:37 ` Sven Köhler
2024-04-18 7:31 ` Li Nan [this message]
2024-04-18 22:07 ` Sven Köhler
2024-04-18 22:11 ` Sven Köhler
2024-05-07 7:32 ` Mariusz Tkaczyk
2024-05-28 22:57 ` Sven Köhler
2024-06-12 14:36 ` Mariusz Tkaczyk
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=cffea7de-edf4-c97b-3fc7-c87038123593@huaweicloud.com \
--to=linan666@huaweicloud.com \
--cc=linux-raid@vger.kernel.org \
--cc=sven.koehler@gmail.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 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).