From: Daniel Pittman <daniel@rimspace.net>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: [RFCI] How best to partition MD/raid devices in 2.6
Date: Fri, 14 Nov 2003 16:27:51 +1100 [thread overview]
Message-ID: <87smkrecyw.fsf@enki.rimspace.net> (raw)
In-Reply-To: <16308.18387.142415.469027@notabene.cse.unsw.edu.au> (Neil Brown's message of "Fri, 14 Nov 2003 14:11:15 +1100")
On Fri, 14 Nov 2003, Neil Brown wrote:
[...]
> 3/ define minor numbers of block-major-9 that are larger than 255 to
> have 6 bits of partitioning information. i.e.
> 9,0 -> md0
> 9,1 -> md1
> ...
> 9,255 -> md255
> 9,256 -> md256
> 9,257 -> md256p1
> 9,257 -> md256p2
> ...
> 9,320 -> md257
> 9,321 -> md257p1
> ...
> This has least impact on other system and is in some ways simplest,
> but it has the problem of lack of uniformity. You wouldn't be able
> to partition md0, but that isn't a big problem as long as you can
> partition some md arrays.
How about assigning the partition space above
9,0 => md0
9,1 => md1
...
9,257 => md0p1
9,258 => md0p2
...
9,320 => md1p1
That should be sensibly backward compatible, I think, and still allow
all the MD devices to be partitioned.
Daniel
--
No, no, you're not thinking, you're just being logical.
-- Niels Bohr
next prev parent reply other threads:[~2003-11-14 5:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 3:11 [RFCI] How best to partition MD/raid devices in 2.6 Neil Brown
2003-11-14 5:09 ` viro
2003-11-14 5:32 ` Neil Brown
2003-11-14 5:21 ` Daniel Gryniewicz
2003-11-14 5:30 ` Neil Brown
2003-11-14 10:16 ` Lars Marowsky-Bree
2003-11-14 18:29 ` Jeff Garzik
2003-11-14 21:44 ` Matt Domsch
2003-11-14 22:45 ` viro
2003-11-17 0:46 ` Automatic Write Reallocation Enable, question? Guy
2003-11-14 5:27 ` Daniel Pittman [this message]
2003-11-14 6:10 ` [RFCI] How best to partition MD/raid devices in 2.6 viro
2003-11-14 7:39 ` Luca Berra
2003-11-14 8:04 ` Paul Jakma
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=87smkrecyw.fsf@enki.rimspace.net \
--to=daniel@rimspace.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).