Linux LVM users
 help / color / mirror / Atom feed
From: Peter T. Breuer <ptb@lab.it.uc3m.es>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Re: Software raid on top of lvm logical volume
Date: Sat, 30 Oct 2004 18:55:55 +0200	[thread overview]
Message-ID: <rltc52-8uk.ln1@triangulo.it.uc3m.es> (raw)
In-Reply-To: 41814060.4040400@mikebabcock.ca

Michael T. Babcock <mike@mikebabcock.ca> wrote:
> Theo Van Dinter wrote:
> 
> >On Thu, Oct 28, 2004 at 12:02:06AM +0200, Eric Monjoin wrote:
> >  
> >
> >>I would like to know if it's possible (works perfectly) to create a 
> >>software mirror (md0) on top of  2 LVM logical volumes :
> >>    
> >>
> >
> >You'd usually want to make your raid devices first, then put LVM on
> >top of it.  I can't really think of any benefits of doing it the other
> >way around.
> >  
> >
> 
> I've thought about this numerous times -- there is the distinct resizing 
> advantage.  Namely, if I create a software RAID partition, I can't 
> resize it afterward without destroying it.  I have for example, on 
> occasion, had three disks set up where 1/3 of each was devoted to a 
> RAID-0 very fast striping set for data transfers that had to be fast but 
> if they were lost it wasn't critical, and 2/3 was set up as RAID-5 for 
> reliability of another set of data.

That would be LVM over raid, not the other way round. You make a raid0
out of 1/3 of each disk (set up a partition on each) nd a raid5 out of
2/3 of each disk. Then you combine and/or divvy up the two raid areas
using lvm.

If you have lvm under raid, you STILL can't change the size of the
raided device without remaking it completely, so what's the point?  (or
does lvm somehow magically permit raid0 resizing on the fly above it -
that would be just about possible, but would require cooperation).

Peter

  reply	other threads:[~2004-10-30 18:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-27 22:02 [linux-lvm] Software raid on top of lvm logical volume Eric Monjoin
2004-10-28  1:17 ` Theo Van Dinter
2004-10-28  6:01   ` Eric Monjoin
2004-10-28  6:35     ` Luca Berra
2004-10-28 19:17       ` [linux-lvm] " Peter T. Breuer
2004-11-01 16:01         ` Michael T. Babcock
2004-11-01 16:51           ` Erik Ohrnberger
2004-11-01 22:03             ` Clint Byrum
2004-11-01 22:07               ` Theo Van Dinter
2004-11-02 15:46             ` Michael T. Babcock
2004-10-28 18:54   ` [linux-lvm] " Michael T. Babcock
2004-10-30 16:55     ` Peter T. Breuer [this message]
2004-10-30 17:10     ` [linux-lvm] What is the best way to configure LVM + RAID? Erik Ohrnberger
2004-10-31 17:34       ` [linux-lvm] " Peter T. Breuer
2004-10-30 17:27     ` [linux-lvm] Software raid on top of lvm logical volume Theo Van Dinter
2004-10-30 19:22       ` [linux-lvm] LVM DISK DIE "KieZz"
2004-10-31 16:48     ` [linux-lvm] Software raid on top of lvm logical volume Markus Baertschi
2004-11-01  6:46       ` Scott Serr
2004-11-01 15:38       ` Michael T. Babcock
2004-11-01 17:02         ` [linux-lvm] " Peter T. Breuer
  -- strict thread matches above, loose matches on Subject: below --
2004-11-02  0:33 Kai Leibrandt

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=rltc52-8uk.ln1@triangulo.it.uc3m.es \
    --to=ptb@lab.it.uc3m.es \
    --cc=linux-lvm@redhat.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