linux-kernel - Re: Strange raid device numbering

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4CAF089B.40204@turmel.org>
Date:	Fri, 08 Oct 2010 08:03:39 -0400
From:	Phil Turmel <philip@...mel.org>
To:	"J.A. Magallón" <jamagallon@....com>
CC:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: Strange raid device numbering

Hi J.A.,

On 10/07/2010 07:43 PM, J.A. Magallón wrote:
> Hi...
> 
> I'm running kernel 2.6.36-rc6.
> I have just built a simple raid0 array with two disks, and I followed what I
> had always done:

[snip /]

> Strangely, after I reboot, the system insists in numbering it as
> md127, instead of md0.
> 
> Why ?
> How can I force it to be md0 ? (its half aesthetics, half curiosity...)

I'm gonna guess that you have some combination of an initramfs, and/or you
don't have an /etc/mdadm.conf, and/or you haven't updated your initramfs with
the latest copy of it.

Raid auto-assembly in the kernel uses the minor numbers in the superblock (if
it can).  Assembly by mdadm without instructions from mdadm.conf uses minor
numbers from 127 and down.  (This may have changed in mdadm in the last few
months, but I recently switched from kernel auto-assembly to initramfs
assembly, so I can't say for sure.)

I've chosen to *not* use mdadm.conf, and find all of my devices with "LABEL="
syntax.

HTH,

Phil
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/