From: Launchpad Bug Tracker <1920211@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1920211] Re: shrink option for discard (for bad host-filesystems and -backup solutions)
Date: Wed, 14 Jul 2021 04:17:22 -0000 [thread overview]
Message-ID: <162623624243.32682.15592464145494581263.malone@loganberry.canonical.com> (raw)
In-Reply-To: 161616435594.712.2426714645893097472.malonedeb@soybean.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1920211
Title:
shrink option for discard (for bad host-filesystems and -backup
solutions)
Status in QEMU:
Expired
Bug description:
When using discard=unmap for virtio or scsi devices with QCOW2 images,
space discarded by the guest will be unmaped on the host, which is
basically great!
This will turn the QCOW2 image into a sparse file which is efficient
for most scenarios. But it may be that you need to avoid big sparse
files on your host. For example because you need to use a backup
solution which doesn't support sparse files well. Or maybe the QCOW2
image is on a filesystem mount which doesn't support sparse files at
all.
For those scenarios an alternative option for the discard setting (discard=shrink) would be great, so that the QCOW2 file itself gets shrunken again.
I'm not sure about how the initial growing* of QCOW2 images is implemented and if there are maybe limitations. But I hope it may be possible do the inverse and actually shrink (not sparse) an QCOW2 image with internally discarded blocks.
I'm using Qemu-5.2.0 and Linux >= 5.3 (host and guest).
*If you use "qemu-img create -f qcow2 ..." withOUT the "preallocation"
option.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1920211/+subscriptions
prev parent reply other threads:[~2021-07-14 4:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 14:32 [Bug 1920211] [NEW] shrink option for discard (for bad host-filesystems and -backup solutions) kolAflash
2021-05-14 18:53 ` [Bug 1920211] " Thomas Huth
2021-07-14 4:17 ` Launchpad Bug Tracker [this message]
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=162623624243.32682.15592464145494581263.malone@loganberry.canonical.com \
--to=1920211@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 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).