linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Will LVM2 ever be able to do striped mirrors "raid 10"?
Date: Mon, 13 Apr 2009 13:25:59 +0100	[thread overview]
Message-ID: <49E32F57.8020105@redhat.com> (raw)
In-Reply-To: <49DF2403.10009@Calva.COM>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Hughes wrote:
> malahal@us.ibm.com wrote:
>> John Hughes [john@Calva.COM] wrote:
>>  
>>> John Hughes wrote:
>>>    
>>>>                if (lp->stripes > 1) {
>>>>                        log_error("mirrors and stripes are currently "
>>>>                                  "incompatible");
>>>>                        return 0;
>>>>                }
>>>>
>>>> Should I just stick with mdadm for my mirroring and striping needs?
>>>>       
>>
>> You can do it today with some hassle or wait until someone implements a
>> feature called 'generic layering'. The feature really means, treat some
>> LVs as PVs!
>>
>> How can you do raid10 today? Create two raid0 LVs. Lets us call these
>> lvgroup0/lv0 and lvgroup0/lv1. Now create raid1 lv in lvgroup1 where
>> lvgroup1's PVs are lvgroup0/lv0 and lvgroup0/lv1.
>>
>> Isn't that a rai10 volume?

No, it's a RAID 0+1 (RAID01/mirror of stripes).

> To increase the chances of surviving a double-disk failure it would be
> better to raid-0 a bunch of raid-1's.

This is RAID1+0 (RAID10/stripe of mirrors) - it's usually preferable to
0+1 not only because of the improved redundancy but also the individual
mirror sets can have failures and recover independently. When a strip
set in a RAID0+1 fails the entire mirror must be re-synchronised giving
longer recovery times and more performance degradation during the rebuild.

> Are we sure there are no deadlock problems with LVM2 layered on top of
> LVM2?

Stacked volumes work fine, there's just limited support in the tools for
creating them without going to a lot of manual effort at the moment.

Regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAknjL1cACgkQ6YSQoMYUY96uPACeNwylwf1aeZuAzYxHWGJhH7Je
LHMAnjLy4NB77gUiABVUkiKeCAMpbGU4
=lv0v
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2009-04-13 12:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 13:11 [linux-lvm] Will LVM2 ever be able to do striped mirrors "raid 10"? John Hughes
2009-04-09  7:17 ` [linux-lvm] Will LVM2 ever be able to do striped mirrors "raid 10"? >>> Use HARDWARE RAID CONTROLLERS Axel Werner
2009-04-09 10:57   ` John Hughes
2009-04-09 13:41     ` Stuart D. Gathman
2009-04-09 11:45   ` Bryn M. Reeves
2009-04-09 13:10     ` Mark H. Wood
2009-04-09 14:40   ` Greg Bledsoe
2009-04-09 18:37   ` Harald Milz
2009-04-17  8:32   ` Luca Berra
2009-04-10  8:26 ` [linux-lvm] Will LVM2 ever be able to do striped mirrors "raid 10"? John Hughes
2009-04-10 10:19   ` malahal
2009-04-10 10:48     ` John Hughes
2009-04-12 13:54       ` Drew
2009-04-13 12:25       ` Bryn M. Reeves [this message]
2009-04-13 14:30         ` Sandeep K Sinha
2009-04-13 10:37           ` Mark Krenz
2009-04-20  8:02           ` Bryn M. Reeves

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=49E32F57.8020105@redhat.com \
    --to=bmr@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).