public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: Neil Brown <neilb@suse.de>
Cc: Goswin von Brederlow <goswin-v-b@web.de>,
	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 13:17:46 +0200	[thread overview]
Message-ID: <87skisnmed.fsf@frosties.localdomain> (raw)
In-Reply-To: <18971.6239.413944.47540@notabene.brown> (Neil Brown's message of "Tue, 26 May 2009 08:14:55 +1000")

Neil Brown <neilb@suse.de> writes:

> On Monday May 25, goswin-v-b@web.de wrote:
>> 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

How would you do this? Worst case you can have a LV made up of totaly
non linear PEs, meaning lots of 4MB (default PE size) big chunks in
random order on random disks.

Do you create a raid1/5 for each stripe? You surely run out of md
devices.

Create dm mappings for all stripe 0s, stripe 1s, stripe 2s, ... and
then a raid1/5 over those stripe devices?

What if the LV has segments with different raid configurations (number
of disks in a stripe or even different levels)? Create a raid for each
segment and then a dm mapping for a linear raid?


You can get a flood of intermediate devices there. A /proc/mdstat with
200 entries would be horrible. iostat output would be totaly
useless. ...

MfG
        Goswin

  reply	other threads:[~2009-05-26 11:17 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
2009-05-26 11:17           ` Goswin von Brederlow [this message]
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=87skisnmed.fsf@frosties.localdomain \
    --to=goswin-v-b@web.de \
    --cc=Marcin.Labun@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=greg.freemyer@gmail.com \
    --cc=jacek.danecki@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --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