From: Neil Brown <neilb@cse.unsw.edu.au>
To: Wakko Warner <wakko@animx.eu.org>
Cc: viro@parcelfarce.linux.theplanet.co.uk,
Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>,
Ezra Nugroho <ezran@goshen.edu>,
linux-kernel@vger.kernel.org
Subject: Re: partitions in meta devices
Date: Wed, 7 May 2003 10:06:18 +1000 [thread overview]
Message-ID: <16056.19962.192303.994466@notabene.cse.unsw.edu.au> (raw)
In-Reply-To: message from Wakko Warner on Monday May 5
On Monday May 5, wakko@animx.eu.org 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?
>
> I recall an MdPart patch for the kernel that would allow this, however, it
> was way too buggy for real use. google for mdpart.
Unreported bugs don't get fixed ... or did I miss your report?
Work great for me on most of my servers.
NeilBrown
next prev parent reply other threads:[~2003-05-06 23:54 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
2003-05-05 19:57 ` Carl-Daniel Hailfinger
2003-05-05 21:38 ` Wakko Warner
2003-05-07 0:06 ` Neil Brown [this message]
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=16056.19962.192303.994466@notabene.cse.unsw.edu.au \
--to=neilb@cse.unsw.edu.au \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=ezran@goshen.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
--cc=wakko@animx.eu.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).