All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: linux-raid@vger.kernel.org
Subject: Re: Partitioning a RAID device
Date: Thu, 05 Sep 2002 18:00:57 +0400	[thread overview]
Message-ID: <3D776399.AC6BD33E@tls.msk.ru> (raw)
In-Reply-To: Pine.LNX.4.30.0209040912270.11782-100000@jaded.cynicism.com

Derek Vadala wrote:
> 
> On Wed, 4 Sep 2002, Arne Wiebalck wrote:
> 
> > is it possible to have partitions on a RAID device?
> >
> > [...]
> >
> > Anything I am missing here?
> 
> You first need to patch your kernel so that the md driver and md devices
> support partitioning. Check out
> http://cgi.cse.unsw.edu.au/~neilb/patches/linux-stable/ for the patches.

Hmm, interesting.  What's those patches are for?  What's their status?
Are they just experiments, proof-of-concept, or intended for general
use?  Are there any interdependances of the set of 5 md-related patches
for 2.4.19?  Some more information on this all?  Discussions?  Official
2.4/2.5 status of this work?  Relation with e.g. LVM?  Iteraction with
devfs for mdp?  Device nodes assignment (i.e. what will become mpa, mpb
etc when one have md0, md1 etc)?  (There are quite a few aspects mentioned
on the above page, mostly nfs-, ext[23]- and md-related stuff, but this is
linux-raid list :)

Errm, so many question... ;)

BTW, still don't know which is "better" -- have several md arrays for every
filesystem/whatether, or have one md array and split it using e.g. lvm or
using this mdp method?  (Two different point of view: system resource usage
should be less for one large md array, but will this one large array handle
load as effective as several independant ones?)

Thanks.

/mjt

  reply	other threads:[~2002-09-05 14:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-04 12:51 Partitioning a RAID device Arne Wiebalck
2002-09-04 16:13 ` Derek Vadala
2002-09-05 14:00   ` Michael Tokarev [this message]
2002-09-06  5:21     ` Neil Brown
2002-09-05 15:42   ` Arne Wiebalck
2002-09-06  5:15     ` Neil Brown
2002-09-09  7:38       ` Arne Wiebalck

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=3D776399.AC6BD33E@tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux-raid@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.