From: Fam Zheng <famz@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: kwolf@redhat.com,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
stefanha@redhat.com, Qemu-block <qemu-block@nongnu.org>,
dgilbert@redhat.com, qemu-devel@nongnu.org,
Vladimir Sementsov-Ogievskiy <vsementsov@parallels.com>,
"Denis V. Lunev" <den@odin.com>
Subject: Re: [Qemu-devel] [PATCH v5 00/12] Dirty bitmaps migration
Date: Wed, 27 Jan 2016 09:17:25 +0800 [thread overview]
Message-ID: <20160127011725.GB31409@ad.usersys.redhat.com> (raw)
In-Reply-To: <56A7F9E9.7000809@redhat.com>
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
next prev parent reply other threads:[~2016-01-27 1:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 15:29 [Qemu-devel] [PATCH v5 00/12] Dirty bitmaps migration Vladimir Sementsov-Ogievskiy
2015-05-13 15:29 ` [Qemu-devel] [PATCH 01/12] hbitmap: serialization Vladimir Sementsov-Ogievskiy
2015-05-13 15:29 ` [Qemu-devel] [PATCH 02/12] block: BdrvDirtyBitmap serialization interface Vladimir Sementsov-Ogievskiy
2015-05-13 15:29 ` [Qemu-devel] [PATCH 03/12] block: tiny refactoring: minimize hbitmap_(set/reset) usage Vladimir Sementsov-Ogievskiy
2015-05-13 15:29 ` [Qemu-devel] [PATCH 04/12] block: add meta bitmaps Vladimir Sementsov-Ogievskiy
2015-05-28 22:13 ` John Snow
2015-05-13 15:30 ` [Qemu-devel] [PATCH 05/12] block: add bdrv_next_dirty_bitmap() Vladimir Sementsov-Ogievskiy
2015-05-13 15:30 ` [Qemu-devel] [PATCH 06/12] qapi: add dirty-bitmaps migration capability Vladimir Sementsov-Ogievskiy
2015-05-13 15:30 ` [Qemu-devel] [PATCH 07/12] migration: add migration/block-dirty-bitmap.c Vladimir Sementsov-Ogievskiy
2015-06-02 21:56 ` John Snow
2015-05-13 15:30 ` [Qemu-devel] [PATCH 08/12] iotests: maintain several vms in test Vladimir Sementsov-Ogievskiy
2015-05-13 15:30 ` [Qemu-devel] [PATCH 09/12] iotests: add add_incoming_migration to VM class Vladimir Sementsov-Ogievskiy
2015-05-13 15:30 ` [Qemu-devel] [PATCH 10/12] qapi: add md5 checksum of last dirty bitmap level to query-block Vladimir Sementsov-Ogievskiy
2015-05-13 15:30 ` [Qemu-devel] [PATCH 11/12] iotests: add dirty bitmap migration test Vladimir Sementsov-Ogievskiy
2015-06-02 22:07 ` John Snow
2015-05-13 15:30 ` [Qemu-devel] [PATCH 12/12] migration/qemu-file: make functions qemu_(get/put)_string public Vladimir Sementsov-Ogievskiy
2015-05-21 13:51 ` [Qemu-devel] [PATCH v5 00/12] Dirty bitmaps migration Vladimir Sementsov-Ogievskiy
2015-05-21 13:57 ` Denis V. Lunev
2015-05-21 16:44 ` John Snow
2015-05-26 14:48 ` Denis V. Lunev
2015-05-26 14:51 ` Denis V. Lunev
2015-05-28 20:09 ` John Snow
2015-05-28 20:56 ` Denis V. Lunev
2015-06-02 22:17 ` John Snow
2015-06-05 10:51 ` Denis V. Lunev
2016-01-26 8:45 ` Vladimir Sementsov-Ogievskiy
2016-01-26 22:57 ` John Snow
2016-01-27 1:17 ` Fam Zheng [this message]
2015-06-02 22:12 ` John Snow
2015-06-03 9:10 ` Vladimir Sementsov-Ogievskiy
2015-06-12 22:16 ` John Snow
2015-06-19 16:57 ` Denis V. Lunev
2015-06-19 17:38 ` John Snow
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=20160127011725.GB31409@ad.usersys.redhat.com \
--to=famz@redhat.com \
--cc=den@odin.com \
--cc=dgilbert@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@parallels.com \
--cc=vsementsov@virtuozzo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.