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
