qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-stable@nongnu.org, qemu-devel@nongnu.org,
	Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PULL v2 7/7] block/backup: disable copy_range for compressed backup
Date: Tue,  6 Aug 2019 13:59:52 +0200	[thread overview]
Message-ID: <20190806115952.8456-8-mreitz@redhat.com> (raw)
In-Reply-To: <20190806115952.8456-1-mreitz@redhat.com>

From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>

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
9ded4a011496.

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>
---
 block/backup.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/block/backup.c b/block/backup.c
index 1ee271f9f1..b26c22c4b8 100644
--- a/block/backup.c
+++ b/block/backup.c
@@ -657,7 +657,7 @@ BlockJob *backup_job_create(const char *job_id, BlockDriverState *bs,
     job->cluster_size = cluster_size;
     job->copy_bitmap = copy_bitmap;
     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),
                                         blk_get_max_transfer(job->target));
     job->copy_range_size = MAX(job->cluster_size,
-- 
2.21.0



  parent reply	other threads:[~2019-08-06 12:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 11:59 [Qemu-devel] [PULL v2 0/7] Block patches for 4.1.0-rc4 Max Reitz
2019-08-06 11:59 ` [Qemu-devel] [PULL v2 1/7] backup: Copy only dirty areas Max Reitz
2019-08-06 11:59 ` [Qemu-devel] [PULL v2 2/7] iotests: Test backup job with two guest writes Max Reitz
2019-08-06 11:59 ` [Qemu-devel] [PULL v2 3/7] util/hbitmap: update orig_size on truncate Max Reitz
2019-08-06 11:59 ` [Qemu-devel] [PULL v2 4/7] iotests: Test incremental backup after truncation Max Reitz
2019-08-06 11:59 ` [Qemu-devel] [PULL v2 5/7] mirror: Only mirror granularity-aligned chunks Max Reitz
2019-08-06 11:59 ` [Qemu-devel] [PULL v2 6/7] iotests: Test unaligned blocking mirror write Max Reitz
2019-08-06 11:59 ` Max Reitz [this message]
2019-08-06 14:44 ` [Qemu-devel] [PULL v2 0/7] Block patches for 4.1.0-rc4 Peter Maydell

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=20190806115952.8456-8-mreitz@redhat.com \
    --to=mreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).