block/backup: disable copy_range for compressed backup
Enabled by default copy_range ignores compress option. It's definitely
unexpected for user.
It's broken since introduction of copy_range usage in backup in
9ded4a0114
.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Message-id: 20190730163251.755248-3-vsementsov@virtuozzo.com
Reviewed-by: John Snow <jsnow@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Cc: qemu-stable@nongnu.org
Signed-off-by: Max Reitz <mreitz@redhat.com>
This commit is contained in:
parent
19ba4651fe
commit
110571be4e
@ -657,7 +657,7 @@ BlockJob *backup_job_create(const char *job_id, BlockDriverState *bs,
|
|||||||
job->cluster_size = cluster_size;
|
job->cluster_size = cluster_size;
|
||||||
job->copy_bitmap = copy_bitmap;
|
job->copy_bitmap = copy_bitmap;
|
||||||
copy_bitmap = NULL;
|
copy_bitmap = NULL;
|
||||||
job->use_copy_range = true;
|
job->use_copy_range = !compress; /* compression isn't supported for it */
|
||||||
job->copy_range_size = MIN_NON_ZERO(blk_get_max_transfer(job->common.blk),
|
job->copy_range_size = MIN_NON_ZERO(blk_get_max_transfer(job->common.blk),
|
||||||
blk_get_max_transfer(job->target));
|
blk_get_max_transfer(job->target));
|
||||||
job->copy_range_size = MAX(job->cluster_size,
|
job->copy_range_size = MAX(job->cluster_size,
|
||||||
|
Loading…
Reference in New Issue
Block a user