Hide Forgot
Description of problem: qcow2 converting error when -o cluster_size <= 2048 Version-Release number of selected component (if applicable): qemu-img-0.12.1.2-2.275.el6.x86_64 qemu-kvm-0.12.1.2-2.275.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. # qemu-img convert -f qcow2 -O qcow2 /mnt/linux/RHEL-Server-6.2-32-virtio.qcow2 /home/kvm_autotest_root/images/RHEL-Server-6.2-32-virtio.qcow2 -o cluster_size=2048 -p qemu-img: error while writing sector 47898624: Unknown error 1610389504 2. 3. Actual results: qemu-img: error while writing sector 47898624: Unknown error 1610389504 Expected results: works well like converting with "-o cluster_size=4096" Additional info:
Please run the same test on RHEL6.2 to figure out if this is a regression.
(In reply to comment #2) > Please run the same test on RHEL6.2 to figure out if this is a regression. nope, RHEL6.2 GA still fails, but unlike 6.3, it didn't mention at which sector. # qemu-img convert -f qcow2 -O qcow2 /mnt/linux/RHEL-Server-6.2-32-virtio.qcow2 /home/kvm_autotest_root/images/RHEL-Server-6.2-32-virtio.qcow2 -o cluster_size=2048 -p qemu-img: error while writing qemu-img-0.12.1.2-2.209.el6.x86_64
reporduce this issue with steps and environment as follows: #uname -r 2.6.32-262.el6.x86_64 #rpm -q qemu-kvm qemu-kvm-0.12.1.2-2.278.el6.x86_64 steps: 1)qemu-img convert -f qcow2 -O qcow2 tracing-run-rhel6.3-copy1.qcow2 tracing-run-rhel6.3-copy2.qcow2 -o cluster_size=2048 -p results: qemu-img: error while writing sector 28430336: Unknown error 1610174464 verify this issue with steps and environment as follows: #uname -r 2.6.32-262.el6.x86_64 #rpm -q qemu-kvm qemu-kvm-0.12.1.2-2.282.el6.x86_64 steps: 1)# qemu-img convert -f qcow2 -O qcow2 tracing-run-rhel6.3-copy1.qcow2 tracing-run-rhel6.3-copy2.qcow2 -o cluster_size=2048 -p (100.00/100%) according to above test results ,this issue has been fixed.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No Documentation Needed
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. http://rhn.redhat.com/errata/RHBA-2012-0746.html