Can't create partitions on raid, --auto=mdp not possible

Can't create partitions on raid, --auto=mdp not possible

[Dexter Filmore]

While I'm at migrating data to a new array I thought I get rid of LVM and 
partition the array directly - spares me one extra layer that I don't need.

Now, I can cfdisk md1 just fine and sfdisk -d shows me the partitions 
md1p[1-4], but as soon as I want to mkfs, I get:

-------------
# LC_ALL=en_EN mkfs.ext3 -O dir_index -E stride=16 -m 0 /dev/md1p1
mke2fs 1.40-WIP (14-Nov-2006)
Could not stat /dev/md1p1 --- No such file or directory

The device apparently does not exist; did you specify it correctly?
-------------

And lo and behold: in /dev no trace of md1p1 or md1/p1 or whatever. Only md1.


When assembling I get:

# mdadm -A -s
mdadm: that --auto option not compatable with device named /dev/md1

Here's my mdadm.conf:
DEVICE partitions
ARRAY /dev/md1 level=raid5 num-devices=5 auto=mdp 
 UUID=f2352335:f8654106:19a59613:120d8f39

This is debian 4.0r3 with kernel 2.6.22 from etch-backports and mdadm 2.5.6.

What do I have here? Version conflict? 

Dex


-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@ 
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------

http://www.vorratsdatenspeicherung.de

Re: Can't create partitions on raid, --auto=mdp not possible

[Dexter Filmore]

Forgot: line I used to create:

mdadm -C /dev/md1 -v -n 5 -l 5 -a p /dev/sd[abcd]1 missing


-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@ 
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------

http://www.vorratsdatenspeicherung.de

Re: Can't create partitions on raid, --auto=mdp not possible

[michael]

Quoting Dexter Filmore <Dexter.Filmore@gmx.de>:

> While I'm at migrating data to a new array I thought I get rid of LVM and
> partition the array directly - spares me one extra layer that I don't need.
>
> Now, I can cfdisk md1 just fine and sfdisk -d shows me the partitions
> md1p[1-4], but as soon as I want to mkfs, I get:
>
> -------------
> # LC_ALL=en_EN mkfs.ext3 -O dir_index -E stride=16 -m 0 /dev/md1p1
> mke2fs 1.40-WIP (14-Nov-2006)
> Could not stat /dev/md1p1 --- No such file or directory
>
> The device apparently does not exist; did you specify it correctly?
> -------------
>
> And lo and behold: in /dev no trace of md1p1 or md1/p1 or whatever. Only md1.
>
>
> When assembling I get:
>
> # mdadm -A -s
> mdadm: that --auto option not compatable with device named /dev/md1
>
> Here's my mdadm.conf:
> DEVICE partitions
> ARRAY /dev/md1 level=raid5 num-devices=5 auto=mdp
>  UUID=f2352335:f8654106:19a59613:120d8f39
>
> This is debian 4.0r3 with kernel 2.6.22 from etch-backports and mdadm 2.5.6.
>
> What do I have here? Version conflict?

It should work, but I *sorta* remember there might be a bug in the  
raid device name for that version of mdadm.
The quick fix would be name your raid device /dev/md_d0 .
After its created, try partitioning it and rebooting.
You should hopefully then be able to mkfs your /dev/md_d0p1 and  
/dev/md_d0p2 and so on.

Cheers,
Mike

Re: Can't create partitions on raid, --auto=mdp not possible

[Michal Soltys]

Dexter Filmore wrote:
> 
> And lo and behold: in /dev no trace of md1p1 or md1/p1 or whatever. Only md1.
> 

Either /dev/md_d1p1 or /dev/md/d1p1. Check DEVICE NAMES section and 
--auto options explanation in mdadm(8)

How nodes are created, depends on command line options explicitly 
provided, mdadm.conf (globally in CREATE and per-device in ARRAY) as 
well as udev rules (currently default rules ignore partitionable raids, 
so just kernel-name device node is created under /dev).