From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41307) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnNq4-0004FC-7Z for qemu-devel@nongnu.org; Wed, 29 Apr 2015 04:59:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YnNq1-0000zb-2n for qemu-devel@nongnu.org; Wed, 29 Apr 2015 04:59:28 -0400 Message-ID: <5540985D.9080406@huawei.com> Date: Wed, 29 Apr 2015 16:37:49 +0800 From: Gonglei MIME-Version: 1.0 References: <20150423121953.GG2177@work-vm> <5538E459.5030801@redhat.com> <20150424020149.GL2723@ad.nay.redhat.com> <5539A78D.1020206@cn.fujitsu.com> <5539F4F6.10507@redhat.com> <5539F702.7040708@cn.fujitsu.com> <20150424085841.GC2139@work-vm> <553A070E.8030909@redhat.com> <553A0F18.4010501@cn.fujitsu.com> <553A0EA3.9080400@redhat.com> <20150427093741.GA15658@stefanha-thinkpad.redhat.com> <55409678.5000002@redhat.com> In-Reply-To: <55409678.5000002@redhat.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH COLO v3 01/14] docs: block replication's description List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , Stefan Hajnoczi Cc: Kevin Wolf , Yang Hongyang , Fam Zheng , qemu block , armbru@redhat.com, jcody@redhat.com, Jiang Yunhong , Dong Eddie , "Dr. David Alan Gilbert" , qemu devel , zhanghailiang , Max Reitz , Lai Jiangshan On 2015/4/29 16:29, Paolo Bonzini wrote: > > > On 27/04/2015 11:37, Stefan Hajnoczi wrote: >>>> But it's only for the failover case. Quorum (or a new >>>> block/colo.c driver or filter) is fine for normal colo >>>> operation. >> Perhaps this patch series should mirror the Secondary's disk to a >> Backup Secondary so that the system can be protected very quickly >> after failover. >> >> I think anyone serious about fault tolerance would deploy a Backup >> Secondary, otherwise the system cannot survive two failures >> unless a human administrator is lucky/fast enough to set up a new >> Secondary. > > Let's do one thing at a time. Otherwise nothing of this is going to > be ever completed... > Yes, and the continuous backup feature is on our TODO list. We hope this series (including basic functions and COLO framework) can be upstream first. Regards, -Gonglei