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:
Created the snapshot chain as base -> sn1 -> sn2. Boot guest with the created image and created temporary files fbase, fsn1, and fsn2 in turn. Commit the changes of sn2 to the base image. Found the temporary files in the guest are changed as below:
base: fbase, fsn1, and fsn2
sn1: fbase, and fsn1
sn2: fbase, fsn1, and fsn2
Checked the scenario with Max(@mreitz), it is expected. But I think below statement explained by Max should be added to the qemu-img manpage. It will help to create a better understanding of the feature.
> If you commit the changes from an image into one in its backing chain,
> all of the intermediate images become obsolete and actually invalid.
> Therefore, in this case, sn1 may no longer be used after the commit
> operation.
Date: Thu, 26 Oct 2017 09:59:47 +0200
From: Max Reitz <mreitz>
Subject: [Qemu-devel] [PATCH] qemu-img.1: Image invalidation on qemu-img commit
To: qemu-block
Cc: Kevin Wolf <kwolf>, qemu-devel, Max Reitz <mreitz>
qemu-img commit invalidates all images between base and top. This
should be mentioned in the man page.
Suggested-by: Ping Li <pingl>
Signed-off-by: Max Reitz <mreitz>
---
qemu-img.texi | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
Checked the manpage, found below descriptions were added.
Note that after a commit operation all images between
base and the top image will be invalid and may return garbage
data when read. For this reason, "-b" implies "-d" (so that the
top image stays valid).
Set the bug as verified.
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.
https://access.redhat.com/errata/RHBA-2018:3443
Description of problem: Created the snapshot chain as base -> sn1 -> sn2. Boot guest with the created image and created temporary files fbase, fsn1, and fsn2 in turn. Commit the changes of sn2 to the base image. Found the temporary files in the guest are changed as below: base: fbase, fsn1, and fsn2 sn1: fbase, and fsn1 sn2: fbase, fsn1, and fsn2 Checked the scenario with Max(@mreitz), it is expected. But I think below statement explained by Max should be added to the qemu-img manpage. It will help to create a better understanding of the feature. > If you commit the changes from an image into one in its backing chain, > all of the intermediate images become obsolete and actually invalid. > Therefore, in this case, sn1 may no longer be used after the commit > operation.