unexpectedly and is allocated again?
If it was not accessing the image from more than one process, any other
exceptions I can test for?
Thanks
leijian
From: Eric Blake
Date: 2015-04-07 23:27
To: Kevin Wolf; leijian
CC: qemu-devel; stefanha
Subject: Re: [Qemu-devel] [Snapshot Bug?]Qcow2 meta data
On 04/07/2015 03:33 AM, Kevin Wolf wrote:
> More specifically, did you take care to never access your image from
> more than one process (except if both are read-only)? It happens
> occasionally that people use 'qemu-img snapshot' while the VM is
> running. This is wrong and can corrupt the image.
Am 03.04.2015 um 12:04 hat leijian geschrieben:
> Hi all,
>
> There was a problem about qcow2 image file happened in my serval vms and I
> could not figure it out,
> so have to ask for some help.
> [...]
> I think the problem is relate to the snapshot create, delete. But I cant
> reproduce it .
Hi all,
There was a problem about qcow2 image file happened in my serval vms and I
could not figure it out,
so have to ask for some help.
Here is the thing:
At first, I found there were some data corruption in a vm, so I did qemu-img
check to all my vms.
parts of check report:
3-Leaked clust
Hi all,
There was a problem about qcow2 image file happened in my serval vms and I
could not figure it out,
so have to ask for some help.
Here is the thing:
At first, I found there were some data corruption in a vm, so I did qemu-img
check to all my vms.
parts of check report:
3-Leaked clust
