Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Fixed upstream with 3e5feb6202149e8a963a33b911216e40d790f1d7, we'll see whether a backport for rhev-7.3.0 is needed or whether that commit will be included by rebase.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-2546.html
Description of problem: qemu-img-rhev-2.3.0-18.el7.x86_64 and qemu-img-rhev-2.3.0-1.el7.x86_64, Both hit this issue. e.g # qemu-img convert -c -f qcow2 -O qcow2 /home/win7-64-bak.qcow2 /home/win7-64-bak-compress.qcow2 qemu-img: error while compressing sector 9263232: Input/output error Version-Release number of selected component (if applicable): qemu-img-rhev-2.3.0-18.el7.x86_64 3.10.0-304.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.# qemu-img info /home/win7-64-bak.qcow2 image: /home/win7-64-bak.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 26G cluster_size: 65536 Format specific information: compat: 0.10 refcount bits: 16 2.# qemu-img convert -c -f qcow2 -O qcow2 /home/win7-64-bak.qcow2 /home/win7-64-bak-compress.qcow2 qemu-img: error while compressing sector 9263232: Input/output error 3.# qemu-img info /home/win7-64-bak-compress.qcow2 image: /home/win7-64-bak-compress.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 2.0G cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false 4.# qemu-img check /home/win7-64-bak-compress.qcow2 No errors were found on the image. 70497/655360 = 10.76% allocated, 98.46% fragmented, 97.99% compressed clusters Image end offset: 2147614720 Actual results: Expected results: Additional info: