[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH RFC v2 0/5] block: add block-dirty-bitmap-populate job
From: |
Peter Krempa |
Subject: |
Re: [PATCH RFC v2 0/5] block: add block-dirty-bitmap-populate job |
Date: |
Mon, 18 May 2020 16:52:45 +0200 |
User-agent: |
Mutt/1.13.4 (2020-02-15) |
On Wed, May 13, 2020 at 23:49:17 -0400, John Snow wrote:
> Hi,
>
> This is a new (very small) block job that writes a pattern into a
> bitmap. The only pattern implemented is the top allocation information.
>
> This can be used to "recover" an incremental bitmap chain if an external
> snapshot was taken without creating a new bitmap first: any writes made
> to the image will be reflected by the allocation status and can be
> written back into a bitmap.
>
> This is useful for e.g. libvirt managing backup chains if a user creates
> an external snapshot outside of libvirt.
I've dusted-off my patches for using this blockjob for this very
specific case and it works for me.
Tested-by: Peter Krempa <address@hidden>
For now I'll continue the integration with other blockjobs where we
merge bitmaps.
- [PATCH RFC v2 1/5] block: add bitmap-populate job, (continued)
- [PATCH RFC v2 1/5] block: add bitmap-populate job, John Snow, 2020/05/13
- [PATCH RFC v2 2/5] blockdev: combine DriveBackupState and BlockdevBackupState, John Snow, 2020/05/13
- [PATCH RFC v2 3/5] qmp: expose block-dirty-bitmap-populate, John Snow, 2020/05/13
- [PATCH RFC v2 4/5] iotests: move bitmap helpers into their own file, John Snow, 2020/05/13
- [PATCH RFC v2 5/5] iotests: add 287 for block-dirty-bitmap-populate, John Snow, 2020/05/13
- Re: [PATCH RFC v2 0/5] block: add block-dirty-bitmap-populate job,
Peter Krempa <=