qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Benoît Canet" <benoit.canet@irqsave.net>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kwolf@redhat.com, pbonzini@redhat.com,
	"Benoît Canet" <benoit.canet@gmail.com>,
	qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [RFC 00/12] Qorum disk image corruption resiliency
Date: Thu, 2 Aug 2012 21:22:38 +0200	[thread overview]
Message-ID: <20120802192237.GA2075@irqsave.net> (raw)
In-Reply-To: <87y5lxi2jl.fsf@codemonkey.ws>

> I'm not entirely sure I understand the use-case all that well.
> 
> Wouldn't the more typical approach be RAID-5 and the use of parity
> instead of relying on voting?
> 
> Quorum doesn't work well with an odd number of disks whereas RAID-5
> does.  You also get significantly more usable disk space with RAID-5
> then with voting.
> 

Hello,

Use case:

A customer using NFS want to setup redudancy across multiple separate
rooms of the same datacenter.
In this case only the network is common.

Testing prove that synchronisation between high end storage applicances
fail in this case.
Something else is required.

With raid5 a small network glitch between the hypervisor and one
of the filer can bring down a while md raid-5 disk.
This involve a rebuild of this disk using heavy parity computation.
(imagine the load with many disk images)
Properly done qorum will correct the error on the fly.

Quorum can correct bitflips induced by the network raid5 cannot.
(bad case ethernet cable sitting around power cord)

Quorum require only two read out of three to reach majority in the
best case.

Some well known cloud provider already use quorum in their setup

Regards,

Benoît

> Regards,
> 
> Anthony Liguori
> 

  reply	other threads:[~2012-08-02 19:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02 10:16 [Qemu-devel] [RFC 00/12] Qorum disk image corruption resiliency Benoît Canet
2012-08-02 10:16 ` [Qemu-devel] [RFC 01/12] qorum: Add GPL v2+ header file Benoît Canet
2012-08-02 14:04   ` Eric Blake
2012-08-02 14:55     ` Benoît Canet
2012-08-02 16:07   ` Andreas Färber
2012-08-02 16:47     ` Benoît Canet
2012-08-02 10:16 ` [Qemu-devel] [RFC 02/12] qorum: Add QorumSingleAIOCB and QorumAIOCB Benoît Canet
2012-08-02 10:16 ` [Qemu-devel] [RFC 03/12] qorum: Create BDRVQorumState and BlkDriver and do init Benoît Canet
2012-08-02 10:16 ` [Qemu-devel] [RFC 04/12] qorum: Add qorum_open() Benoît Canet
2012-08-02 10:16 ` [Qemu-devel] [RFC 05/12] qorum: Add qorum_close() Benoît Canet
2012-08-02 10:16 ` [Qemu-devel] [RFC 06/12] qorum: Add qorum_getlength() Benoît Canet
2012-08-02 10:16 ` [Qemu-devel] [RFC 07/12] qorum: Add qorum_aio_writev and its dependencies Benoît Canet
2012-08-02 10:16 ` [Qemu-devel] [RFC 08/12] blkverify: Make blkverify_iovec_clone() and blkverify_iovec_compare() public Benoît Canet
2012-08-02 10:16 ` [Qemu-devel] [RFC 09/12] qorum: Add qorum_co_flush() Benoît Canet
2012-08-02 10:16 ` [Qemu-devel] [RFC 10/12] qorum: Add qorum_aio_readv Benoît Canet
2012-08-02 10:16 ` [Qemu-devel] [RFC 11/12] qorum: Add qorum mechanism Benoît Canet
2012-08-02 10:16 ` [Qemu-devel] [RFC 12/12] qorum: build feature into QEMU Benoît Canet
2012-08-02 16:06   ` Andreas Färber
2012-08-02 13:17 ` [Qemu-devel] [RFC 00/12] Qorum disk image corruption resiliency Eric Blake
2012-08-02 13:28   ` Benoît Canet
2012-08-02 18:14 ` Anthony Liguori
2012-08-02 19:22   ` Benoît Canet [this message]
2012-08-03  9:21     ` Stefan Hajnoczi
2012-08-03 16:14 ` Blue Swirl
2012-08-03 19:11   ` Benoît Canet

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=20120802192237.GA2075@irqsave.net \
    --to=benoit.canet@irqsave.net \
    --cc=anthony@codemonkey.ws \
    --cc=benoit.canet@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.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).