All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Коренберг Марк" <603878@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 603878] Re: [Feature request] qemu-img option about recompressing
Date: Thu, 22 Apr 2021 05:47:35 -0000	[thread overview]
Message-ID: <161907045677.10328.8967999942061695218.launchpad@wampee.canonical.com> (raw)
In-Reply-To: 20100710070634.22855.99257.malonedeb@soybean.canonical.com

** Changed in: qemu
       Status: Incomplete => New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/603878

Title:
  [Feature request] qemu-img option about recompressing

Status in QEMU:
  New

Bug description:
  Suppose I have a fresh compressed qcow2 image. After some time the
  data were recorded without compression. I decide to make "QEMU-IMG
  convert" for that image to reduce its size.

  I want a new option, which selects between the two algorithms overdriven images:
  1. extract all / compress again when converting images (in the current implementation)
  2. compress only uncompressed blocks and just copy the compressed blocks without re-compression.

  This option is only needed when converting compressed image to
  compressed and the compression algorithm is the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/603878/+subscriptions


  parent reply	other threads:[~2021-04-22  6:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-10  7:06 [Qemu-devel] [Bug 603878] [NEW] [Feature request] qemu-img option about recompressing Коренберг Марк
2010-07-10  7:19 ` [Qemu-devel] [Bug 603878] " Коренберг Марк
2016-11-09 20:25 ` Thomas Huth
2021-04-22  3:53 ` Thomas Huth
2021-04-22  5:47 ` Коренберг Марк [this message]
2021-05-02  5:16 ` Thomas Huth

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=161907045677.10328.8967999942061695218.launchpad@wampee.canonical.com \
    --to=603878@bugs.launchpad.net \
    --cc=qemu-devel@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 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.