linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: Greg Freemyer <greg.freemyer@gmail.com>,
	Dan Williams <dan.j.williams@intel.com>,
	raz ben yehuda <raziebe@013.net>,
	linux-raid@vger.kernel.org,
	Jacek Danecki <jacek.danecki@intel.com>,
	"Labun, Marcin" <Marcin.Labun@intel.com>
Subject: Re: Subject: [001/002 ] raid0 reshape
Date: Tue, 26 May 2009 08:14:55 +1000	[thread overview]
Message-ID: <18971.6239.413944.47540@notabene.brown> (raw)
In-Reply-To: message from Goswin von Brederlow on Monday May 25

On Monday May 25, goswin-v-b@web.de wrote:
> Greg Freemyer <greg.freemyer@gmail.com> writes:
> 
> > ==> What I mean by raid equivalent levels
> >
> > More and more arrays allow the user to simply say "give me a 100 GB
> > logical volume with Raid 5 equivalent protection.  The array then
> > looks at the drives it has available and puts together the necessary
> > pieces.  As drives are added, removed it moves the data around under
> > its own control, but maintains the raid equivalent protection.
> >
> > Especially when working with dozens of drives and lots of logical
> > volumes it makes life much easier.  Admittedly it may come at a cost
> > of not being able to specify raid levels with the specificity that
> > mdraid currently allows.
> >
> > ==>
> >
> > The reason I ask if this is the goal is that doing so may factor into
> > decisions about how reshaping is implemented.
> >
> > Greg
> 
> That really seems to scream for LVM to support more raid levels. It
> already has linear, raid0 and raid1 support (although I have no idea
> how device mapper raid1 compares to md raid1).

Note that LVM (a suite of user-space tools) could conceivably use
md/raid1, md/raid5 etc. The functionality doesn't have to go in dm.

Neil

> 
> Those should be fleshed out more and also support raid 4/5/6 for what
> you ask.
> 
> MfG
>         Goswin

  parent reply	other threads:[~2009-05-25 22:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-02 21:46 Subject: [001/002 ] raid0 reshape raz ben yehuda
2009-05-10 22:31 ` Neil Brown
2009-05-12 16:59   ` Raz
2009-05-19 18:09 ` Dan Williams
2009-05-19 22:27   ` Raz
2009-05-21 11:48   ` Neil Brown
2009-05-21 12:33     ` OT: busting a gut (was Re: Subject: [001/002 ] raid0 reshape) John Robinson
2009-05-21 19:20     ` Subject: [001/002 ] raid0 reshape Greg Freemyer
2009-05-25 12:19       ` Goswin von Brederlow
2009-05-25 20:06         ` Raz
2009-05-27 21:55           ` Bill Davidsen
2009-05-25 22:14         ` Neil Brown [this message]
2009-05-26 11:17           ` Goswin von Brederlow
2009-05-26 11:51             ` Neil Brown
2009-05-28 19:07               ` Goswin von Brederlow
2009-05-22  7:53     ` Dan Williams
2009-05-23 22:33     ` Raz

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=18971.6239.413944.47540@notabene.brown \
    --to=neilb@suse.de \
    --cc=Marcin.Labun@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=goswin-v-b@web.de \
    --cc=greg.freemyer@gmail.com \
    --cc=jacek.danecki@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=raziebe@013.net \
    /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).