From: Ezra Nugroho <ezran@goshen.edu>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: partitions in meta devices
Date: 05 May 2003 11:57:14 -0500 [thread overview]
Message-ID: <1052153834.29676.219.camel@ezran.goshen.edu> (raw)
In-Reply-To: <3EB693B1.9020505@gmx.net>
On Mon, 2003-05-05 at 11:39, Carl-Daniel Hailfinger wrote:
> Ezra Nugroho wrote:
> > I am curious if partitioning meta devices is allowed or not.
> >
> > I just created a software raid array, md0 with 240G logical size.
> > I want to partition that into two, 100G and the rest.
> >
> > I used fdisk to create the partitions, and it worked, result:
> >
> > bangalore exports # fdisk /dev/md0
> >
> > Command (m for help): p
> >
> > Disk /dev/md0: 247.0 GB, 247044636672 bytes
> > 2 heads, 4 sectors/track, 60313632 cylinders
> > Units = cylinders of 8 * 512 = 4096 bytes
> >
> > Device Boot Start End Blocks Id System
> > /dev/md0p1 1 24414064 97656254 83 Linux
> > /dev/md0p2 24414065 60313632 143598272 83 Linux
> >
> >
> > however, I couldn't create any file system for them, or mount them.
> > /dev/md0px just don't exist.
> >
> > Do I need to partition the drives first before creating the raids?
> > I use devfs instead of file based /dev
>
> Please reboot after partitioning.
I did. Nothing changed. fdisk reported the changes still.
next prev parent reply other threads:[~2003-05-05 16:31 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 [this message]
2003-05-05 16:59 ` Carl-Daniel Hailfinger
2003-05-05 17:21 ` Ezra Nugroho
2003-05-05 19:16 ` viro
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
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=1052153834.29676.219.camel@ezran.goshen.edu \
--to=ezran@goshen.edu \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--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 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).