linux-kernel - 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-next>] [day] [month] [year] [list]

Date:	Fri, 8 Oct 2010 01:43:18 +0200
From:	"J.A. Magallón" <jamagallon@....com>
To:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Strange raid device numbering

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:

raid=/dev/md0
ndisk=2
disks="/dev/sda1 /dev/sdb1"
block=4
chunk=256

stride=$((chunk/block))
stripe=$((stride*ndisk))

for i in $disks
do
    mdadm --zero-superblock --force $i
done
mdadm -C -f -v $raid --level=0 --chunk=$chunk -n $ndisk $disks
sleep 5
mdadm -S $raid
mdadm --assemble $raid $disks
mkfs.ext4 -b $((block*1024)) -E stride=$stride,stripe-width=$stripe $raid

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...)

TIA

-- 
J.A. Magallon <jamagallon()ono!com>     \               Software is like sex:
                                         \         It's better when it's free
--
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/