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.
Did you have a clean shutdown of qemu before you ran qemu-img check? Otherwise
this is not a bug. The trick of lazy refcounts is exactly that images can be
left in an inconsistent state, protected by the dirty flag.
(In reply to Kevin Wolf from comment #4)
> Did you have a clean shutdown of qemu before you ran qemu-img check?
> Otherwise
> this is not a bug. The trick of lazy refcounts is exactly that images can be
> left in an inconsistent state, protected by the dirty flag.
Hi Kevin,
I execute the "stop" qemu command before check image, then got "4110 errors were found on the image."
Description of problem: guest image get "ERROR cluster" when create with lazy_refcounts=on, No errors were found if create without lazy_refcounts=on Version-Release number of selected component (if applicable): How reproducible: kernel-3.10.0-111.el7.x86_64 qemu-kvm-rhev-1.5.3-53.el7.x86_64 qemu-img-rhev-1.5.3-53.el7.x86_64 Steps to Reproduce: 1. Create a fresh qcow2 image qemu-img create -f qcow2 -o lazy_refcounts=on /root/RHEL-Server-7.0-64-virtio.qcow2 20G 2. install guest /usr/libexec/qemu-kvm \ -name 'virt-tests-vm1' \ -sandbox off \ -M pc \ -nodefaults \ -vga cirrus \ -device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=03 \ -drive id=drive_image1,if=none,cache=none,snapshot=off,aio=native,file=/root/RHEL-Server-7.0-64-virtio.qcow2 \ -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=1,bus=pci.0,addr=04 \ -device virtio-net-pci,mac=9a:ca:cb:cc:cd:ce,id=idh06wPW,netdev=idXCB3Or,bus=pci.0,addr=05 \ -netdev tap,id=idXCB3Or,vhost=on,vhostfd=28,fd=27 \ -m 4096 \ -smp 4,maxcpus=4,cores=2,threads=1,sockets=2 \ -cpu 'SandyBridge',+kvm_pv_unhalt \ -drive id=drive_cd1,if=none,snapshot=off,aio=native,media=cdrom,file=/root/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/isos/linux/RHEL7.0-Server-x86_64.iso \ -device ide-cd,id=cd1,drive=drive_cd1,bootindex=2,bus=ide.0,unit=0 \ -drive id=drive_unattended,if=none,snapshot=off,aio=native,media=cdrom,file=/root/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/images/rhel70-64/ks.iso \ -device ide-cd,id=unattended,drive=drive_unattended,bootindex=3,bus=ide.0,unit=1 \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -kernel '/root/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/images/rhel70-64/vmlinuz' \ -append 'ksdevice=link ks=cdrom:/dev/sr1:/ks.cfg nicdelay=60 console=ttyS0,115200 console=tty0' \ -initrd '/root/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/images/rhel70-64/initrd.img' \ -vnc :0 \ -rtc base=utc,clock=host,driftfix=slew \ -boot order=cdn,once=d,menu=off \ -no-kvm-pit-reinjection \ -no-shutdown \ -enable-kvm 3. after installation, boot guest and update guest kernel 4. check guest image qemu-img check /root/RHEL-Server-7.0-64-virtio.qcow2 Actual results: got error infos: ERROR OFLAG_COPIED data cluster: l2_entry=80000000f08b0000 refcount=0 ERROR OFLAG_COPIED data cluster: l2_entry=80000000f08c0000 refcount=0 ERROR OFLAG_COPIED data cluster: l2_entry=80000000f08d0000 refcount=0 ERROR OFLAG_COPIED data cluster: l2_entry=80000000f08e0000 refcount=0 ERROR OFLAG_COPIED data cluster: l2_entry=80000000f08f0000 refcount=0 4558 errors were found on the image. Data may be corrupted, or further writes to the image may corrupt it. 62174/327680 = 18.97% allocated, 13.23% fragmented, 0.00% compressed clusters Image end offset: 4075880448 Expected results: No errors were found on the image. Additional info: