linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sven Köhler" <sven.koehler@gmail.com>
To: 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: Sat, 13 Apr 2024 23:37:12 +0200	[thread overview]
Message-ID: <5a4a9b82-2082-4d25-906d-ee01b10fad65@gmail.com> (raw)
In-Reply-To: <fe14b4b4-9ab2-93f5-85a8-3416d79dffa2@huaweicloud.com>

Hi,

Am 11.04.24 um 04:25 schrieb Li Nan:
> Hi,
>
> 在 2024/4/11 4:59, Sven Köhler 写道:
>> Hi,
>>
>> Am 10.04.24 um 03:56 schrieb Li Nan:
>>> Hi, Köhler
>>>
>>> 在 2024/4/9 7:31, Sven Köhler 写道:
>
> [...]
>
>>
>> I should have mentioned the mdadm and kernel version. I am using 
>> mdadm 4.3-2 and linux-lts 6.6.23-1 on Arch Linux.
>>
>> I created the array very similar to what you did:
>> mdadm --create /dev/md4 --level=6 --raid-devices=4 --metadata=0.90 
>> /dev/sd[abcd]4
>>
>> My mdadm.conf looks like this:
>> DEVICE partitions
>> ARRAY /dev/md/4 metadata=0.90  UUID=...
>>
>> And /proc/partitions looks like this:
>>
>> major minor  #blocks  name
>>     8        0 2930266584 sda
>>     8        1    1048576 sda1
>>     8        2   33554432 sda2
>>     8        3   10485760 sda3
>>     8        4 2885176775 sda4
>>     8       16 2930266584 sdb
>>     8       17    1048576 sdb1
>>     8       18   33554432 sdb2
>>     8       19   10485760 sdb3
>>     8       20 2885176775 sdb4
>>     8       32 2930266584 sdc
>>     8       33    1048576 sdc1
>>     8       34   33554432 sdc2
>>     8       35   10485760 sdc3
>>     8       36 2885176775 sdc4
>>     8       48 2930266584 sdd
>>     8       49    1048576 sdd1
>>     8       50   33554432 sdd2
>>     8       51   10485760 sdd3
>>     8       52 2885176775 sdd4
>>
>>
>> Interestingly, sda, sdb, etc. are included. So "DEVICE partitions" 
>> actually considers them.
>>
>
> 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.

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


  reply	other threads:[~2024-04-13 21:37 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 [this message]
2024-04-18  7:31         ` Li Nan
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=5a4a9b82-2082-4d25-906d-ee01b10fad65@gmail.com \
    --to=sven.koehler@gmail.com \
    --cc=linan666@huaweicloud.com \
    --cc=linux-raid@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).