This bug has been copied from bug #572825 and has been proposed to be backported to 5.5 z-stream (EUS).
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: Cause: qcow2 code didn't flush metadata writes, risking integrity on case of crashes. Consequence: http://wiki.qemu.org/Features/Qcow2DataIntegrity#Metadata_update_ordering.2C_Part_2 Fix: Flush after metadata writes. Use bdrv_(p)write_sync for metadata writes. Result: qcow2 data integrity after host crashes is improved.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,7 +1 @@ -Cause: qcow2 code didn't flush metadata writes, risking integrity on case of crashes. +Following writing metadata to a QCOW2 disk image, metadata was not flushed, which could have potentially caused the disk image to become corrupted in the event of system disruption (such as a power outage). With this update, metadata is flushed after being written, thus increasing QCOW2 image integrity, and decreasing the likelihood of image corruption.- -Consequence: http://wiki.qemu.org/Features/Qcow2DataIntegrity#Metadata_update_ordering.2C_Part_2 - -Fix: Flush after metadata writes. Use bdrv_(p)write_sync for metadata writes. - -Result: qcow2 data integrity after host crashes is improved.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0536.html