From: viro@parcelfarce.linux.theplanet.co.uk
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: Ezra Nugroho <ezran@goshen.edu>, linux-kernel@vger.kernel.org
Subject: Re: partitions in meta devices
Date: Mon, 5 May 2003 20:16:04 +0100 [thread overview]
Message-ID: <20030505191604.GC10374@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <3EB69883.8090609@gmx.net>
On Mon, May 05, 2003 at 06:59:47PM +0200, Carl-Daniel Hailfinger wrote:
> OK. Maybe I wasn't clear enough.
> 1. Partition a drive
> 2. Reboot
> 3. Now the kernel should see the partitions and let you create file
> systems on them.
>
> You rebooted and fdisk sees the partitions now. Fine. Please try to
> mke2fs /dev/md0p1
> That should work. If it doesn't, devfs could be the problem.
No, it should not. And devfs, for once, has nothing to do with it.
RAID devices (md*) have _one_ (1) minor allocated to each. Consequently,
they could not be partitioned by any kernel - there is no device numbers
to be assigned to their partitions.
> Could you please tell us which kernel version you're using?
What would be much more interesting, which kernel are _you_ using
and what device numbers, in your experience, do these partitions get?
next prev parent reply other threads:[~2003-05-05 19:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 16:44 partitions in meta devices Ezra Nugroho
2003-05-05 16:39 ` Carl-Daniel Hailfinger
2003-05-05 16:57 ` Ezra Nugroho
2003-05-05 16:59 ` Carl-Daniel Hailfinger
2003-05-05 17:21 ` Ezra Nugroho
2003-05-05 19:16 ` viro [this message]
2003-05-05 19:57 ` Carl-Daniel Hailfinger
2003-05-05 21:38 ` Wakko Warner
2003-05-07 0:06 ` Neil Brown
2003-05-05 17:17 ` Bernd Schubert
2003-05-05 17:18 ` Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2003-05-05 22:49 Chuck Ebbert
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=20030505191604.GC10374@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=ezran@goshen.edu \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.