Ok, thanks for clarifying that. So it looks like the temporary snapshot was already merged/deleted. As part of that operation, vdsm calculates how large the original volume would have to be (LV size) in order to guarantee that the base volume has enough space for the merge to complete. It looks like in this case we decided that value was the virtual size + 10% for qcow2 metadata. If your base volume was only about 16G allocated prior to all of this than it seems we were way too conservative. Did you remove the snapshot quickly after the move completed? One thing that could cause this is if you wrote about 12-15 GB of data into the that disk after moving but before deleting the temporary snapshot.
Do you happen to have the vdsm logs from the host running the VM and the host that was acting SPM (if different) from during the time you experienced this issue? On Mon, Feb 20, 2017 at 10:02 AM, Gianluca Cecchi <gianluca.cec...@gmail.com > wrote: > On Mon, Feb 20, 2017 at 3:38 PM, Adam Litke <ali...@redhat.com> wrote: > >> Hi Gianluca. This is most likely caused by the temporary snapshot we >> create when performing live storage migration. Please check your VM for >> snapshots and delete the temporary one. >> >> > Hi Adam, > as you see from my attachment, there is one line for snapshots, the > current one, and no others. > So the VM is without snapshots. > See bigger frame here: > https://drive.google.com/file/d/0BwoPbcrMv8mvbDZaVFpvd1Ayd0k/ > view?usp=sharing > > Gianluca > > -- Adam Litke
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users