linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Raz <raziebe@gmail.com>
Cc: Goswin von Brederlow <goswin-v-b@web.de>, linux-raid@vger.kernel.org
Subject: Re: Subject: [001/002 ] raid0 reshape
Date: Wed, 27 May 2009 17:55:09 -0400	[thread overview]
Message-ID: <4A1DB6BD.50000@tmr.com> (raw)
In-Reply-To: <5d96567b0905251306v4b1b2ef5p9268063ad81eacd8@mail.gmail.com>

Raz wrote:
> It is not clear to me why Linux has both LVM and md,waste of
> development effort to my opinion. Adding to that brtfs/zfs reaching
> mainline, Linux will have 3-4 volume managers to maintain.
> why not join hands  and come up with a single unify system?
>   

Linux is about choice? One size doesn't fit all?

I see no reason for raid anything in LVM, it's a duplication of effort. 
By the same token, I think building everything into the file system, 
while it seems nice, means that you lose the flexibility of being able 
to control the devices, the raid behavior, and the allocation, each 
independently. I'll be the first to admit that I occasionally abuse that 
flexibility (story coming one of these days), but it's there.

As long as there's a tool to help the novice put the pieces together 
without in-depth technical expertise, I don't think limiting options to 
just one is desirable at all.

> On Mon, May 25, 2009 at 3:19 PM, Goswin von Brederlow <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).
>>
>> Those should be fleshed out more and also support raid 4/5/6 for what
>> you ask.
>>     


-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc

"You are disgraced professional losers. And by the way, give us our money back."
    - Representative Earl Pomeroy,  Democrat of North Dakota
on the A.I.G. executives who were paid bonuses  after a federal bailout.



  reply	other threads:[~2009-05-27 21:55 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 [this message]
2009-05-25 22:14         ` Neil Brown
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=4A1DB6BD.50000@tmr.com \
    --to=davidsen@tmr.com \
    --cc=goswin-v-b@web.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=raziebe@gmail.com \
    /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).