linux-kernel - Re: MDADM Software Raid Woes

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

Message-ID: <44f470466dcf22c47f6700502caf9cbd.squirrel@neil.brown.name>
Date:	Fri, 19 Dec 2008 07:06:11 +1100 (EST)
From:	"NeilBrown" <neilb@...e.de>
To:	"Dylan Taft" <d13f00l@...il.com>
Cc:	"Nick Andrew" <nick@...k-andrew.net>, linux-kernel@...r.kernel.org,
	linux-raid@...r.kernel.org
Subject: Re: MDADM Software Raid Woes

On Fri, December 19, 2008 12:08 am, Dylan Taft wrote:
> I may give that a shot.
>
> But it also looks like my major numbers are wrong on the actual device
> nodes?
> brw-r-----  1 root disk   9, 0 Dec 17 19:13 0
> brw-r-----  1 root disk 259, 0 Dec 17 19:13 1
> brw-r-----  1 root disk 259, 1 Dec 17 19:13 2
> brw-r-----  1 root disk 259, 2 Dec 17 19:13 3
>
> Shouldn't this be 9,something, not 259?
>
> If I change the partition type from fd to something else, and don't
> allow the kernel to auto assemble, then assemble manually via mdadm,
> things work right.
> Any idea what could cause thee major numbers to be wrong?

Almost certainly some udev configuration going wrong.
What distro are you running?
Is there are file in /lib/udev/rules.d or /etc/udev/rules.d with 'md'
in the name?  What is in that file?

Prior to 2.6.28, normal md devices (major number 9) could not be
partitioned. You needed to use "mdp" devices (major number close to 254).
To get autodetect to create these use the kernel parameter
"raid=partitionable".

In 2.6.28, partitions don't have to have the same major number as the
base device.
In you case,
  md0 is 9,0
  md1 is 9,1

  md1p1 is 259,0
  md1p2 is 259.1
  md1p3 is 259,2

as you can see, the device nodes have been created with the wrong
name.  In each case the name used is md followed by the last digit
of what should have been used.  udev is the only thing that could have
done that.

Hence my questions about your distro and udev configuration.

NeilBrown

--
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/