A counter variable isn't correctly reset when restarting an allocating request
in qcow2, resulting in corruption in some cases. For details, see
was opened against an Ubuntu release using the same code:
> When using qemu-kvm-1.0 occasionally qcow2 disks will be corrupted.
> [Test Case]
> A test case can be downloaded here:
> Extract the contents and run ./create-disk, then ./test-kvm to test the
> currently installed KVM. Keep in mind that 100GB+ of disk is required to
> run the test.
This bug was introduced in RHEL 6 commit 73ea798d. The first release to contain
this commit is 6.3.
Test this bug according to comment 0,on the following version for twice, first time the result shows GOOD and the second time, the result shows BAD. Attachment will be uploaded.
Could you help confirm my second log (BAD result), does this mean I reproduce the issue?
Created attachment 761775 [details]
Result - GOOD
Created attachment 761776 [details]
Result - BAD
(In reply to Qunfang Zhang from comment #2)
> Hi, Kevin
> Could you help confirm my second log (BAD result), does this mean I
> reproduce the issue?
It's not my test case, so I have to guess the same as you have. But it looks to
me as if you reproduced the issue indeed. It also says:
*** localhost Sun Jun 16 08:05:01 201 Error: Data corruption
Reproduced again on qemu-kvm-rhev-0.12.1.2-2.375.el6.x86_64 on the first attempt. And then verified it for 3 times on qemu-kvm-rhev-0.12.1.2-2.376.el6.x86_64, all the test pass.
0. Make sure host has 100GB+ free disk.
2. Uncompress the lnv-382.tgz
4. Modified "test-kvm" and replace command "kvm" to "/usr/libexec/qemu-kvm".
Result: On the fixed version qemu-kvm-rhev-0.12.1.2-2.376.el6.x86_64, the test passed. I tried 3 times and all passed.
Return value: 0
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.
*** Bug 993611 has been marked as a duplicate of this bug. ***