[Bug 1652459] Re: kvm rbd driver (and maybe others, i.e. qcow2, qed and so on) does not report DISCARD-ZERO flag

[Thomas Huth]

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


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

** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #139
   https://gitlab.com/qemu-project/qemu/-/issues/139

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1652459

Title:
  kvm rbd driver (and maybe others, i.e. qcow2, qed and so on)  does not
  report DISCARD-ZERO flag

Status in QEMU:
  Expired

Bug description:
  # lsblk -D
  NAME   DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO
  sda           0        4K       1G         0
  ├─sda1        0        4K       1G         0
  ├─sda2     1024        4K       1G         0
  └─sda5        0        4K       1G         0

  Last column should be `1` at least for "RBD+discard=unmap" since
  reading from discarded regions in RBD MUST return zeroes. The same
  with QCOW2, QED and sparse raw images. KVM should copy value of this
  flag when real raw device (i.e. real SSD) with discard capability is
  used as virtual disk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1652459/+subscriptions