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.
Kevin, could storage migration interfere with the patches you committed recently that affect caching with BDRV_O_INCOMING? Either by making things better, or by making them much worse.
Would it make any sense for writes to clear BDRV_O_INCOMING?
(In reply to Kevin Wolf from comment #5)
> Is this still reproducible with the latest packages? Looks like a potential
> duplicate of bug 1048575.
Hi Sluo,
Could you have a try and update testing result in the bz?
Best Regards,
Junyi
Description of problem: 1.after completing the configuration of src and des, sometimes qemu will be core dump on des 2. but no occur core dump, from src to des, failed to copy image. Version-Release number of selected component (if applicable): # uname -r 3.10.0-0.rc3.58.el7.x86_64 qemu-kvm-1.5.0-2.el7.x86_64 How reproducible: 50% Steps to Reproduce: 1. des qemu-img create -f qcow2 -o compat=1.1 test1.qcow2 35G /usr/libexec/qemu-kvm -cpu SandyBridge -M pc-i440fx-1.4 -enable-kvm -m 4G -smp 4,sockets=2,cores=2,threads=1 -name scalability-test -uuid 389d06a7-e631-4fae-baf4-87bdb9b5594e -rtc base=localtime,clock=host,driftfix=slew -drive file=/home/test1.qcow3,if=none,id=drive-system-disk,media=disk,format=qcow2,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,bus=pci.0,drive=drive-system-disk,id=system-disk,addr=0x6 -drive file=/home/test2.qcow3,if=none,id=drive-s1-disk,media=disk,format=qcow2,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,bus=pci.0,drive=drive-s1-disk,id=s1-disk,addr=0x7 -drive file=/home/test3.qcow3,if=none,id=drive-s2-disk,media=disk,format=qcow2,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,bus=pci.0,drive=drive-s2-disk,id=s2-disk,addr=0x8 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=00:22:15:27:54:3d,bus=pci.0,addr=0x9 -k en-us -boot menu=on -vnc :0 -vga cirrus -monitor stdio -qmp tcp:0:5555,server,nowait -incoming tcp:0:5888 {"execute": "qmp_capabilities"} { "execute": "nbd-server-start", "arguments": { "addr": { "type": "inet", "data": { "host": "10.66.4.112", "port": "7777" } } } } (qemu) nbd_server_add -w drive-system-disk (qemu) nbd_server_add -w drive-s1-disk (qemu) nbd_server_add -w drive-s2-disk 2. src /usr/libexec/qemu-kvm -cpu SandyBridge -M pc-i440fx-1.4 -enable-kvm -m 4G -smp 4,sockets=2,cores=2,threads=1 -name scalability-test -uuid 389d06a7-e631-4fae-baf4-87bdb9b5594e -rtc base=localtime,clock=host,driftfix=slew -drive file=/home/rhel7cp5.qcow3,if=none,id=drive-system-disk,media=disk,format=qcow2,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,bus=pci.0,drive=drive-system-disk,id=system-disk,addr=0x6 -drive file=/home/new1.qcow3,if=none,id=drive-s1-disk,media=disk,format=qcow2,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,bus=pci.0,drive=drive-s1-disk,id=s1-disk,addr=0x7 -drive file=/home/new2.qcow3,if=none,id=drive-s2-disk,media=disk,format=qcow2,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,bus=pci.0,drive=drive-s2-disk,id=s2-disk,addr=0x8 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=00:22:15:27:56:3d,bus=pci.0,addr=0x9 -k en-us -boot menu=on -vnc :0 -vga cirrus -monitor stdio -qmp tcp:0:5555,server,nowait {"execute": "qmp_capabilities"} { "execute": "drive-mirror", "arguments": { "device": "drive-system-disk", "target": "nbd://10.66.4.112:7777/drive-system-disk", "sync": "full", "format": "raw", "mode": "existing" } } { "execute": "drive-mirror", "arguments": { "device": "drive-s1-disk", "target": "nbd://10.66.4.112:7777/drive-s1-disk", "sync": "full", "format": "raw", "mode": "existing" } } { "execute": "drive-mirror", "arguments": { "device": "drive-s2-disk", "target": "nbd://10.66.4.112:7777/drive-s2-disk", "sync": "full", "format": "raw", "mode": "existing" } } 3. migrate -d tcp:$des-host-ip:$port Actual results: 1. des: (qemu) qemu-system-x86_64: block/qcow2-cache.c:67: qcow2_cache_destroy: Assertion `c->entries[i].ref == 0' failed. 2. {"timestamp": {"seconds": 1370484715, "microseconds": 973943}, "event": "BLOCK_IO_ERROR", "data": {"device": "drive-system-disk", "operation": "write", "action": "stop"}} Expected results: qemu work normally copy image from src to des should be work well Additional info: