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:
make a vmdk format image, then create first external snapshot1 with the backing file, then create second external snapshot2 with snapshot1 as backing file. but it fail to crate snapshot2 with prompt 'No such file or directory'. btw, qcow2 have no such issue.
e.g: base<-----snap1<-------snap2<----...
Version-Release number of selected component (if applicable):
host info:
2.6.32-392.el6.x86_64
qemu-kvm-0.12.1.2-2.376.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.create a vmdk format disk.
# qemu-img create -f vmdk vmdk-data-disk.vmdk 10G
Formatting 'vmdk-data-disk.vmdk', fmt=vmdk size=10737418240 compat6=off zeroed_grain=off
# qemu-img info vmdk-data-disk.vmdk
image: vmdk-data-disk.vmdk
file format: vmdk
virtual size: 10G (10737418240 bytes)
disk size: 12K
2.create first external snapshot1 with the backing file.
# qemu-img create -f vmdk -b vmdk-data-disk.vmdk vmdk-data-snapshot1
Formatting 'vmdk-data-snapshot1', fmt=vmdk size=10737418240 backing_file='vmdk-data-disk.vmdk' compat6=off zeroed_grain=off
# qemu-img info vmdk-data-snapshot1
image: vmdk-data-snapshot1
file format: vmdk
virtual size: 10G (10737418240 bytes)
disk size: 12K
backing file: disk.vmdk
# ls -lh vmdk-data-snapshot1
-rw-r--r--. 1 root root 1.4M Jun 25 17:56 vmdk-data-snapshot1
3.create second external snapshot3 with the backing file.
# qemu-img create -f vmdk -b vmdk-data-snapshot1 vmdk-data-snapshot2
Actual results:
after step 3, it fail to crate snapshot2 with prompt 'No such file or directory'.
# qemu-img create -f vmdk -b vmdk-data-snapshot1 vmdk-data-snapshot2
Could not open 'vmdk-data-snapshot1': No such file or directory
Expected results:
it should can ordinal create external snapshot with vmdk format one by one.
Additional info: