qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Jeff Cody <jcody@redhat.com>, Fam Zheng <famz@redhat.com>,
	qemu-devl <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] more check for replaced node
Date: Thu, 2 Jul 2015 15:48:29 +0100	[thread overview]
Message-ID: <20150702144829.GC950@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <5593A9A4.7010305@cn.fujitsu.com>

[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]

On Wed, Jul 01, 2015 at 04:49:40PM +0800, Wen Congyang wrote:
> On 07/01/2015 04:39 PM, Stefan Hajnoczi wrote:
> > On Thu, Jun 25, 2015 at 02:55:10PM +0800, Wen Congyang wrote:
> >> Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
> >> ---
> >>  block.c               | 5 +++--
> >>  block/mirror.c        | 3 ++-
> >>  blockdev.c            | 2 +-
> >>  include/block/block.h | 3 ++-
> >>  4 files changed, 8 insertions(+), 5 deletions(-)
> > 
> > This patch is missing a commit description.  What is the justification
> > for this change?
> 
> Sorry, I forgot to add commit messages..
> 
> Without this patch, the replace node can be any node, and it can be
> top BDS with BB, or another quorum's child. With this patch, the replace node
> must be this quorum's child.

I think the point of the replace operation was to swap a quorum child
with a new drive.  It sounds like this patch will break that use case?

The idea was that a failed child needs to be replaced.  The user adds a
new -drive and then uses the mirror+replace to include it into the
quorum.  I think the new child is not be part of the quorum BDS graph
until replacement occurs.

Stefan

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-07-02 14:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25  6:55 [Qemu-devel] [PATCH] more check for replaced node Wen Congyang
2015-07-01  8:39 ` Stefan Hajnoczi
2015-07-01  8:49   ` Wen Congyang
2015-07-02 14:48     ` Stefan Hajnoczi [this message]
2015-07-13  2:41       ` Wen Congyang
2015-07-14 12:10         ` Stefan Hajnoczi

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=20150702144829.GC950@stefanha-thinkpad.redhat.com \
    --to=stefanha@redhat.com \
    --cc=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wency@cn.fujitsu.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).