From: Eric Blake <eblake@redhat.com>
To: "Benoît Canet" <benoit.canet@irqsave.net>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, "Benoît Canet" <benoit@irqsave.net>,
stefanha@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH V19 06/12] quorum: Add quorum mechanism.
Date: Fri, 21 Feb 2014 15:09:42 -0700 [thread overview]
Message-ID: <5307CEA6.5050003@redhat.com> (raw)
In-Reply-To: <1393017681-12794-7-git-send-email-benoit.canet@irqsave.net>
[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]
On 02/21/2014 02:21 PM, Benoît Canet wrote:
> From: Benoît Canet <benoit@irqsave.net>
>
> This patchset enables the core of the quorum mechanism.
> The num_children reads are compared to get the majority version and if this
> version exists more than threshold times the guest won't see the error at all.
> +++ b/docs/qmp/qmp-events.txt
> @@ -500,3 +500,39 @@ Example:
>
> Note: If action is "reset", "shutdown", or "pause" the WATCHDOG event is
> followed respectively by the RESET, SHUTDOWN, or STOP events.
> +
> +QUORUM_FAILURE
> +--------------
This should have been inserted in sorted order to match the rest of the
file, rather than at the end. Can be rearranged in a followup patch,
now that this series is queued.
> +
> +Emitted by the Quorum block driver if it fails to establish a quorum.
> +
> +Data:
> +
> +- "reference": device name if defined else node name.
> +- "sector-num": Number of the first sector of the failed read operation.
I'm assuming sector-num is relative to the guest's view of the data?
> +
> +QUORUM_REPORT_BAD
> +-----------------
> +
> +Emitted to report a corruption of a Quorum file.
> +
> +Data:
> +
> +- "ret": The IO return code.
What values is this likely to contain? Is it a finite set, in which
case it would be nice to have a QAPI enum that describes the set of
return codes, rather than a raw number?
I'd like to make sure we are happy with the wire format of this QMP
event before it gets baked into 2.0.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-02-21 22:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 21:21 [Qemu-devel] [PATCH V19 00/12] Quorum block filter Benoît Canet
2014-02-21 21:21 ` [Qemu-devel] [PATCH V19 01/12] quorum: Create quorum.c, add QuorumChildRequest and QuorumAIOCB Benoît Canet
2014-02-21 21:21 ` [Qemu-devel] [PATCH V19 02/12] quorum: Create BDRVQuorumState and BlkDriver and do init Benoît Canet
2014-02-21 21:21 ` [Qemu-devel] [PATCH V19 03/12] quorum: Add quorum_aio_writev and its dependencies Benoît Canet
2014-02-21 21:21 ` [Qemu-devel] [PATCH V19 04/12] blkverify: Extract qemu_iovec_clone() and qemu_iovec_compare() from blkverify Benoît Canet
2014-02-21 21:21 ` [Qemu-devel] [PATCH V19 05/12] quorum: Add quorum_aio_readv Benoît Canet
2014-02-21 21:21 ` [Qemu-devel] [PATCH V19 06/12] quorum: Add quorum mechanism Benoît Canet
2014-02-21 22:09 ` Eric Blake [this message]
2014-02-21 22:30 ` Benoît Canet
2014-02-21 22:38 ` Kevin Wolf
2014-02-21 22:44 ` Eric Blake
2014-02-21 22:50 ` Benoît Canet
2014-02-21 23:32 ` Eric Blake
2014-02-21 22:41 ` Eric Blake
2014-02-21 21:21 ` [Qemu-devel] [PATCH V19 07/12] quorum: Add quorum_getlength() Benoît Canet
2014-02-21 21:21 ` [Qemu-devel] [PATCH V19 08/12] quorum: Add quorum_invalidate_cache() Benoît Canet
2014-02-21 21:21 ` [Qemu-devel] [PATCH V19 09/12] quorum: Add quorum_co_flush() Benoît Canet
2014-02-21 21:21 ` [Qemu-devel] [PATCH V19 10/12] quorum: Implement recursive .bdrv_recurse_is_first_non_filter in quorum Benoît Canet
2014-02-21 21:21 ` [Qemu-devel] [PATCH V19 11/12] quorum: Add quorum_open() and quorum_close() Benoît Canet
2014-02-21 21:57 ` Eric Blake
2014-02-21 21:21 ` [Qemu-devel] [PATCH V19 12/12] quorum: Add unit test Benoît Canet
2014-02-21 21:39 ` [Qemu-devel] [PATCH V19 00/12] Quorum block filter Kevin Wolf
2014-02-21 22:49 ` Eric Blake
2014-02-21 22:58 ` 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=5307CEA6.5050003@redhat.com \
--to=eblake@redhat.com \
--cc=benoit.canet@irqsave.net \
--cc=benoit@irqsave.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).