linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: "viro@parcelfarce.linux.theplanet.co.uk" 
	<viro@parcelfarce.linux.theplanet.co.uk>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: partitions in meta devices
Date: Mon, 5 May 2003 18:49:12 -0400	[thread overview]
Message-ID: <200305051851_MC3-1-3782-9001@compuserve.com> (raw)

>       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?

 These patches appear to contain raid partitioning code of some sort:

   http://www.cse.unsw.edu.au/~neilb/patches/linux-stable/

Only the first 16 md devices can be partitioned, though... major is 60,
minors are 0-15 for md0, 16-31 for md1, etc.



             reply	other threads:[~2003-05-05 22:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-05 22:49 Chuck Ebbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2003-05-05 17:17     ` Bernd Schubert
2003-05-05 17:18   ` Jörn Engel

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=200305051851_MC3-1-3782-9001@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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).