Skip to content

push backup with fleecing

Vladimir Sementsov-Ogievskiy qemu-devel 2 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest6 patches 1 replyIn review
  2. v16 patches 0 repliesSuperseded

Changes in v2 from the cover letter

01: changed to simply check s->target->perm
06: make explicit immutable-source parameter instead of auto-detecting

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/6block/block-copy: use write-unchanged for fleecing schemeblock/block-copy.c+14 -40 replies
2/6block/copy-before-write: require BLK_PERM_WRITE_UNCHANGED for fleecingblock/copy-before-write.c+10 -10 replies
3/6block: share writes on backing child of fleecing nodeblock.c block/copy-before-write.c block/copy-before-write.h+40 -10 replies
4/6block: blk_root(): return non-const pointerblock/block-backend.c include/sysemu/block-backend.h+2 -20 replies
5/6qapi: backup: add immutable-source paramterblock/backup.c block/replication.c blockdev.c +2 more+80 -70 replies
6/6iotests/image-fleecing: test push backup with fleecingtests/qemu-iotests/tests/image-fleecing tests/qemu-iotests/tests/image-fleecing.out+141 -250 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [PATCH v2 for-6.2 0/6] push backup with fleecing

Hi all!

Here is push-backup with fleecing. What is it:

1. Make fleecing scheme

guest blk
|
|root
v
copy-before-write filter -------> temp qcow2

  |                                  |
  |file                              | backing
  V                                  |

active disk <-------------------------

2. Start backup job from temp qcow2 to final remote target (NBD or something)

Benefit in comparison with simple backup job: for remote final target write operations are not very fast. And guest have to wait for copy-before-write operations. With fleecing scheme target for copy-before-write operations is local qcow2 file with faster access than actual backup target. So, guest is less disturbed by copy-before-write operations.

Based-on: <[email protected]>
([PATCH v6 00/33] block: publish backup-top filter)

v2:
01: changed to simply check s->target->perm
06: make explicit immutable-source parameter instead of auto-detecting

Vladimir Sementsov-Ogievskiy (6):
block/block-copy: use write-unchanged for fleecing scheme block/copy-before-write: require BLK_PERM_WRITE_UNCHANGED for fleecing
block: share writes on backing child of fleecing node
block: blk_root(): return non-const pointer
qapi: backup: add immutable-source paramter iotests/image-fleecing: test push backup with fleecing

 qapi/block-core.json                        |  12 ++-
 block/copy-before-write.h                   |   1 +
 include/block/block_int.h                   |   1 +
 include/sysemu/block-backend.h              |   2 +-
 block.c                                     |   3 +-
 block/backup.c                              |  71 ++++++++++++-
 block/block-backend.c                       |   2 +-
 block/block-copy.c                          |  18 +++-
 block/copy-before-write.c                   |  48 ++++++++-
 block/replication.c                         |   2 +-
 blockdev.c                                  |   1 +
 tests/qemu-iotests/tests/image-fleecing     | 105 +++++++++++++++-----
 tests/qemu-iotests/tests/image-fleecing.out |  61 ++++++++++++
 13 files changed, 287 insertions(+), 40 deletions(-)
Signature · 1 line
2.29.2