This is an automated cleanup. This bug report has been moved to QEMU's new bug tracker on gitlab.com and thus gets marked as 'expired' now. Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/264 ** Changed in: qemu Status: New => Expired ** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #264 https://gitlab.com/qemu-project/qemu/-/issues/264 -- 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: Expired 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
