QEMU-Devel Archive on lore.kernel.org
 help / color / Atom feed
* [Qemu-devel] [Bug 1806196] [NEW] qed leaked clusters
@ 2018-12-01 16:57 Коренберг Марк
  2018-12-05 11:07 ` [Qemu-devel] [Bug 1806196] " Alex Bennée
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: Коренберг Марк @ 2018-12-01 16:57 UTC (permalink / raw)
  To: qemu-devel

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Qemu-devel] [Bug 1806196] Re: qed leaked clusters
  2018-12-01 16:57 [Qemu-devel] [Bug 1806196] [NEW] qed leaked clusters Коренберг Марк
@ 2018-12-05 11:07 ` Alex Bennée
  2018-12-18 12:03 ` Stefan Hajnoczi
                   ` (4 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: Alex Bennée @ 2018-12-05 11:07 UTC (permalink / raw)
  To: qemu-devel

** Tags added: qemu-img

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Qemu-devel] [Bug 1806196] Re: qed leaked clusters
  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 ` Коренберг Марк
                   ` (3 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: Stefan Hajnoczi @ 2018-12-18 12:03 UTC (permalink / raw)
  To: qemu-devel

Thanks for reporting this.  QED is not widely used and its features have
been incorporated into qcow2, QEMU's native image format.  Since there
is no development effort behind QED it is unlikely that this bug will be
addressed.  Patches are always welcome though!

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Qemu-devel] [Bug 1806196] Re: qed leaked clusters
  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
                   ` (2 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: Коренберг Марк @ 2018-12-18 18:15 UTC (permalink / raw)
  To: qemu-devel

I think, this bug also can be triggered in qcow2. Unfortunately it is
not so easy for me to find roots of the 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug 1806196] Re: qed leaked clusters
  2018-12-01 16:57 [Qemu-devel] [Bug 1806196] [NEW] qed leaked clusters Коренберг Марк
                   ` (2 preceding siblings ...)
  2018-12-18 18:15 ` Коренберг Марк
@ 2021-04-20  6:49 ` Thomas Huth
  2021-04-20 12:08 ` Коренберг Марк
  2021-05-11  5:36 ` Thomas Huth
  5 siblings, 0 replies; 7+ messages in thread
From: Thomas Huth @ 2021-04-20  6:49 UTC (permalink / raw)
  To: qemu-devel

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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug 1806196] Re: qed leaked clusters
  2018-12-01 16:57 [Qemu-devel] [Bug 1806196] [NEW] qed leaked clusters Коренберг Марк
                   ` (3 preceding siblings ...)
  2021-04-20  6:49 ` Thomas Huth
@ 2021-04-20 12:08 ` Коренберг Марк
  2021-05-11  5:36 ` Thomas Huth
  5 siblings, 0 replies; 7+ messages in thread
From: Коренберг Марк @ 2021-04-20 12:08 UTC (permalink / raw)
  To: qemu-devel

** Changed in: qemu
       Status: Incomplete => New

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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug 1806196] Re: qed leaked clusters
  2018-12-01 16:57 [Qemu-devel] [Bug 1806196] [NEW] qed leaked clusters Коренберг Марк
                   ` (4 preceding siblings ...)
  2021-04-20 12:08 ` Коренберг Марк
@ 2021-05-11  5:36 ` Thomas Huth
  5 siblings, 0 replies; 7+ messages in thread
From: Thomas Huth @ 2021-05-11  5:36 UTC (permalink / raw)
  To: qemu-devel

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


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, back to index

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2021-04-20 12:08 ` Коренберг Марк
2021-05-11  5:36 ` Thomas Huth

QEMU-Devel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/qemu-devel/0 qemu-devel/git/0.git
	git clone --mirror https://lore.kernel.org/qemu-devel/1 qemu-devel/git/1.git
	git clone --mirror https://lore.kernel.org/qemu-devel/2 qemu-devel/git/2.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 qemu-devel qemu-devel/ https://lore.kernel.org/qemu-devel \
		qemu-devel@nongnu.org
	public-inbox-index qemu-devel

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.nongnu.qemu-devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git