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.
Description of problem:
------------------------
when mirroring an entire snapshot chain with QMP option "full"=true, after reopen qemu-kvm is not closing opened base image and "info block" shows backing_file still exists.
Version-Release number of selected component (if applicable):
--------------------------------------------------------------
qemu-kvm-rhev-0.12.1.2-2.286.el6.x86_64
How reproducible:
------------------
100%
Steps to Reproduce:
--------------------
1.boot guest with base
2.
(qemu) snapshot_blkdev drive-virtio-disk0 /root/nfs/sn1 qcow2
(qemu) snapshot_blkdev drive-virtio-disk0 /root/nfs/sn2 qcow2
3.mirror with "full"=true
{ "execute" : "__com.redhat_drive-mirror", "arguments" : { "device" : "drive-virtio-disk0", "target" : "/root/nfs/sn3", "format": "qcow2", "mode": "absolute-paths", "full" : true } }
4.after steady state, reopen to sn3
5.(qemu) info block
drive-virtio-disk0: removable=0 io-status=ok file=/root/nfs/sn3 backing_file=/root/nfs/sn1 ro=0 drv=qcow2 encrypted=0
6.[root@shu nfs]# lsof -p 32084 | grep "/root"
qemu-kvm 32084 root cwd DIR 0,28 4096 2 /root/nfs
qemu-kvm 32084 root 12u REG 0,28 8152940544 16 /root/nfs/sn3
qemu-kvm 32084 root 23r REG 0,28 262144 14 /root/nfs/sn1
qemu-kvm 32084 root 24r REG 0,28 8136949760 12 /root/nfs/win7-64-virtio.qcow2
7.[root@shu nfs]# qemu-img info sn3
image: sn3
file format: qcow2
virtual size: 30G (32212254720 bytes)
disk size: 7.6G
cluster_size: 65536
Actual results:
----------------
sn2 is dropped, sn1 and base are not dropped.
Additional info:
----------------------------
this one is very similar to:
Bug 801449 - qemu-kvm is not closing the merged images files (block_stream)
i have just verified this bug, with simply streaming and mirroring in use but with "full"=false it works correctly, so i think it's better to separate them.
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
Description of problem: ------------------------ when mirroring an entire snapshot chain with QMP option "full"=true, after reopen qemu-kvm is not closing opened base image and "info block" shows backing_file still exists. Version-Release number of selected component (if applicable): -------------------------------------------------------------- qemu-kvm-rhev-0.12.1.2-2.286.el6.x86_64 How reproducible: ------------------ 100% Steps to Reproduce: -------------------- 1.boot guest with base 2. (qemu) snapshot_blkdev drive-virtio-disk0 /root/nfs/sn1 qcow2 (qemu) snapshot_blkdev drive-virtio-disk0 /root/nfs/sn2 qcow2 3.mirror with "full"=true { "execute" : "__com.redhat_drive-mirror", "arguments" : { "device" : "drive-virtio-disk0", "target" : "/root/nfs/sn3", "format": "qcow2", "mode": "absolute-paths", "full" : true } } 4.after steady state, reopen to sn3 5.(qemu) info block drive-virtio-disk0: removable=0 io-status=ok file=/root/nfs/sn3 backing_file=/root/nfs/sn1 ro=0 drv=qcow2 encrypted=0 6.[root@shu nfs]# lsof -p 32084 | grep "/root" qemu-kvm 32084 root cwd DIR 0,28 4096 2 /root/nfs qemu-kvm 32084 root 12u REG 0,28 8152940544 16 /root/nfs/sn3 qemu-kvm 32084 root 23r REG 0,28 262144 14 /root/nfs/sn1 qemu-kvm 32084 root 24r REG 0,28 8136949760 12 /root/nfs/win7-64-virtio.qcow2 7.[root@shu nfs]# qemu-img info sn3 image: sn3 file format: qcow2 virtual size: 30G (32212254720 bytes) disk size: 7.6G cluster_size: 65536 Actual results: ---------------- sn2 is dropped, sn1 and base are not dropped. Additional info: ---------------------------- this one is very similar to: Bug 801449 - qemu-kvm is not closing the merged images files (block_stream) i have just verified this bug, with simply streaming and mirroring in use but with "full"=false it works correctly, so i think it's better to separate them.