From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36418) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aOEjo-0001Sk-KG for qemu-devel@nongnu.org; Tue, 26 Jan 2016 20:17:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aOEjn-0002Xx-Og for qemu-devel@nongnu.org; Tue, 26 Jan 2016 20:17:36 -0500 Date: Wed, 27 Jan 2016 09:17:25 +0800 From: Fam Zheng Message-ID: <20160127011725.GB31409@ad.usersys.redhat.com> References: <555DE2D7.2020200@parallels.com> <555DE431.60703@openvz.org> <555E0B5D.5060302@redhat.com> <556487BF.2000809@openvz.org> <55648887.7080804@odin.com> <55677603.8040506@redhat.com> <556780E8.6000700@odin.com> <556E2B87.5090302@redhat.com> <56A73245.6060001@virtuozzo.com> <56A7F9E9.7000809@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56A7F9E9.7000809@redhat.com> Subject: Re: [Qemu-devel] [PATCH v5 00/12] Dirty bitmaps migration List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: John Snow Cc: kwolf@redhat.com, Vladimir Sementsov-Ogievskiy , stefanha@redhat.com, Qemu-block , dgilbert@redhat.com, qemu-devel@nongnu.org, Vladimir Sementsov-Ogievskiy , "Denis V. Lunev" On Tue, 01/26 17:57, John Snow wrote: > Can we implement a function that, in the event of a disaster, compares > the current state of the drive with the last known good incremental and > populates a bitmap based on the difference? > > Actually, we probably really want this feature around regardless. It'll > allow us to start incremental backup chains from full backups made > before we even knew we wanted to start making them. > > Something like: > > block-dirty-bitmap-diff node=drive0 name=bitmap0 target=/path/to/file > > I like this idea, I think I'll prototype just this little piece, since > it's useful even without postcopy bitmap migration. Good idea! It looks like another type of block job. Fam