From: Thomas Huth <1806196@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1806196] Re: qed leaked clusters
Date: Tue, 20 Apr 2021 06:49:12 -0000 [thread overview]
Message-ID: <161890135235.26945.12740057151670836567.malone@gac.canonical.com> (raw)
In-Reply-To: 154368343637.32200.15942853285785778925.malonedeb@wampee.canonical.com
The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1806196
Title:
qed leaked clusters
Status in QEMU:
Incomplete
Bug description:
There are examples of two QED files which AFAIK does not have any
errors both. But `qemu-img check` says that one of them has 1 leaked
cluster.
I wrote my own tool and it does not find any error. Both files
attached, as well as debug output from my program.
Both files are about 4G in size after unpacking. Unpack with `tar -S`
to handle sparse files.
And also, I know, that QED is deprecated, but anyway, seems qemu-img
has bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1806196/+subscriptions
next prev parent reply other threads:[~2021-04-20 6:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 16:57 [Qemu-devel] [Bug 1806196] [NEW] qed leaked clusters Коренберг Марк
2018-12-05 11:07 ` [Qemu-devel] [Bug 1806196] " Alex Bennée
2018-12-18 12:03 ` Stefan Hajnoczi
2018-12-18 18:15 ` Коренберг Марк
2021-04-20 6:49 ` Thomas Huth [this message]
2021-04-20 12:08 ` Коренберг Марк
2021-05-11 5:36 ` 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=161890135235.26945.12740057151670836567.malone@gac.canonical.com \
--to=1806196@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).