From: Dexter Filmore <Dexter.Filmore@gmx.de>
To: linux-raid@vger.kernel.org
Subject: Can't create partitions on raid, --auto=mdp not possible
Date: Sat, 26 Apr 2008 13:46:03 +0200 [thread overview]
Message-ID: <200804261346.03511.Dexter.Filmore@gmx.de> (raw)
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
next reply other threads:[~2008-04-26 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 11:46 Dexter Filmore [this message]
2008-04-26 11:50 ` Can't create partitions on raid, --auto=mdp not possible Dexter Filmore
2008-04-27 1:38 ` michael
2008-04-27 7:43 ` Michal Soltys
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=200804261346.03511.Dexter.Filmore@gmx.de \
--to=dexter.filmore@gmx.de \
--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).