From: "Benoît Canet" <benoit.canet@irqsave.net>
To: Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, "Benoît Canet" <benoit.canet@gmail.com>,
stefanha@linux.vnet.ibm.com, qemu-devel@nongnu.org,
blauwirbel@gmail.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [RFC V5 09/11] quorum: Add quorum_getlength().
Date: Mon, 27 Aug 2012 21:23:49 +0200 [thread overview]
Message-ID: <20120827192348.GC4498@irqsave.net> (raw)
In-Reply-To: <503BB684.5000007@redhat.com>
Le Monday 27 Aug 2012 à 12:03:48 (-0600), Eric Blake a écrit :
> On 08/27/2012 01:30 AM, Benoît Canet wrote:
> > Signed-off-by: Benoit Canet <benoit@irqsave.net>
> > ---
> > block/quorum.c | 24 ++++++++++++++++++++++++
> > 1 file changed, 24 insertions(+)
>
> Say I'm using a 2/3 quorum. What happens if:
>
> image A and B agree on initial content, but not length
> image B and C agree on length, but not content
>
> Does disagreeing with quorum consensus invalidate that member of the
> quorum from influencing further decisions? If there is a length
> discrepancy, should we declare the quorum failed rather than relying on
> a mere majority vote? Or, if there is a length discrepancy, does
> reading the contents beyond the end of the shorter files consider the
> contents to be okay if the longer files have only NUL bytes in the extra
> length? I'm worried that you haven't fully thought through all the
> scenarios here.
True,
Maybe I shoud just check that every quorum file have the same length
and return 0 on error. This way the quorum in disabled in case of length
discrepancy.
>
> --
> Eric Blake eblake@redhat.com +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
>
next prev parent reply other threads:[~2012-08-27 19:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 7:30 [Qemu-devel] [RFC V5 00/11] Quorum disk image corruption resiliency Benoît Canet
2012-08-27 7:30 ` [Qemu-devel] [RFC V5 01/11] quorum: Create quorum.c, add QuorumSingleAIOCB and QuorumAIOCB Benoît Canet
2012-08-27 7:30 ` [Qemu-devel] [RFC V5 02/11] quorum: Create BDRVQuorumState and BlkDriver and do init Benoît Canet
2012-08-27 7:30 ` [Qemu-devel] [RFC V5 03/11] quorum: Add quorum_open() and quorum_close() Benoît Canet
2012-08-27 17:59 ` Eric Blake
2012-08-27 19:20 ` Benoît Canet
2012-08-27 7:30 ` [Qemu-devel] [RFC V5 04/11] quorum: Add quorum_aio_writev and its dependencies Benoît Canet
2012-08-27 7:30 ` [Qemu-devel] [RFC V5 05/11] blkverify: Extract qemu_iovec_clone() and qemu_iovec_compare() from blkverify Benoît Canet
2012-08-27 7:30 ` [Qemu-devel] [RFC V5 06/11] quorum: Add quorum_co_flush() Benoît Canet
2012-08-27 7:30 ` [Qemu-devel] [RFC V5 07/11] quorum: Add quorum_aio_readv Benoît Canet
2012-08-27 7:30 ` [Qemu-devel] [RFC V5 08/11] quorum: Add quorum mechanism Benoît Canet
2012-08-27 7:30 ` [Qemu-devel] [RFC V5 09/11] quorum: Add quorum_getlength() Benoît Canet
2012-08-27 18:03 ` Eric Blake
2012-08-27 19:23 ` Benoît Canet [this message]
2012-08-27 7:30 ` [Qemu-devel] [RFC V5 10/11] quorum: Add quorum_invalidate_cache() Benoît Canet
2012-08-27 7:30 ` [Qemu-devel] [RFC V5 11/11] quorum: Add quorum_co_is_allocated 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=20120827192348.GC4498@irqsave.net \
--to=benoit.canet@irqsave.net \
--cc=benoit.canet@gmail.com \
--cc=blauwirbel@gmail.com \
--cc=eblake@redhat.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).