linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: Neil Brown <neilb@suse.de>,
	linux-fsdevel@vger.kernel.org,
	Graeme Sheppard <nodes@rillion.net>
Subject: Re: Patent or not patent a new idea
Date: Tue, 26 Jun 2007 13:38:25 -0400	[thread overview]
Message-ID: <20070626173825.GL6652@schatzie.adilger.int> (raw)
In-Reply-To: <OF9DD60090.D627328D-ON88257306.005B2285-88257306.005CBFC6@us.ibm.com>

On Jun 26, 2007  09:53 -0700, Bryan Henderson wrote:
> >md/raid already works happily with different sized drives from
> >different manufacturers ...
> 
> >So I still cannot see anything particularly new.
> 
> As compared to md of conventional disk partitions, it brings the ability 
> to create and delete arrays without shutting down all use of the physical 
> disks (to update the partition tables).  (LVM gives you that too).  It 
> also makes managing space much easier because the component devices don't 
> have to be carved from contiguous space on the physical disks.
> 
> Neither of those benefits is specific to RAID, but you could probably say 
> that RAID multiplies the problems they address.

That's one of the reasons why I liked AIX doing RAID1 on top of LVM.  It
was possible to safely migrate LEs across disks by virtue of creating a
RAID 1 mirror for that LE and then deleting the old copy.  It wouldn't
be too hard to extend the same notion to RAID 5 or RAID 6 on LVM.  You
could even change the RAID level and number of constituent LEs in a RAID
set on an ad-hoc basis because the LVM mappings would allow this to be
efficient.

Unfortunately, Linux still has distinct DM and MD layers and there doesn't
seem to be any work to combine the two into a more powerful single layer.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.


      reply	other threads:[~2007-06-26 17:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25 21:45 Patent or not patent a new idea Graeme Sheppard
2007-06-25 22:04 ` alan
2007-06-25 22:26   ` Graeme Sheppard
2007-06-25 22:33     ` alan
2007-06-25 22:34 ` Attila Kinali
2007-06-25 22:37 ` manningc2
2007-06-26  0:11   ` Bryan Henderson
2007-06-26  1:32 ` Graeme Sheppard
2007-06-26  2:20   ` Neil Brown
2007-06-26  3:20     ` Graeme Sheppard
2007-06-26  3:38       ` Neil Brown
2007-06-26  4:22         ` Graeme Sheppard
2007-06-26  4:33           ` Neil Brown
2007-06-26 16:53         ` Bryan Henderson
2007-06-26 17:38           ` Andreas Dilger [this message]

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=20070626173825.GL6652@schatzie.adilger.int \
    --to=adilger@clusterfs.com \
    --cc=hbryan@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=nodes@rillion.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).