[Qemu-devel] [Bug 1806196] [NEW] qed leaked clusters

From: "Коренберг Марк" <1806196@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1806196] [NEW] qed leaked clusters
Date: Sat, 01 Dec 2018 16:57:16 -0000	[thread overview]
Message-ID: <154368343637.32200.15942853285785778925.malonedeb@wampee.canonical.com> (raw)

Public bug reported:

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.

** Affects: qemu
     Importance: Undecided
         Status: New

** Attachment added: "Example of files"
   https://bugs.launchpad.net/bugs/1806196/+attachment/5217981/+files/bugs.tbz2

** Description changed:

- There are example of two QED files which AFAIK does not have errors
+ There are examples of two QED files which AFAIK does not have errors
  both. But qemu-img check say 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.

** Description changed:

- There are examples of two QED files which AFAIK does not have errors
+ There are examples of two QED files which AFAIK does not have any errors
  both. But qemu-img check say 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.

** Description changed:

  There are examples of two QED files which AFAIK does not have any errors
- both. But qemu-img check say that one of them has 1 leaked cluster.
+ 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
+ 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.

-- 
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:
  New

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