Hi,

we are on OVirt 4.0.4. As explained the situation is as follows:

- On Disk we have the base image and the delata qcow2 file

- Qemu runs only on the base image

- The snapshot in Qemu is tagged as illegal

So you say: "Just retry a live merge and everything will cleanup.= =3D "

Did I get it right?

Markus

-----------------------------------------------

Von: Ala Hino [ahino(a)redhat.com]

Gesendet: Donnerstag, 6. Oktober 2016= 11:=3D 21
An: Markus Stockhausen
Cc: Ovirt Users; Nir Soffer; Adam Litke
Betreff: Re: [ovirt-users] Cleanup illegal snapshot

Hi Markus,

What's the version that you are using?

In oVirt 3.6.6, illegal snapshots could be removed by retrying to live= =3D merge them again. Assuming the previous live merge of the snapshot success= =3D fully completed but the engine failed to get the result, the second live me= =3D rge should do the necessary cleanups at the engine side. See https://bugzilla.redhat.com/1323629

Hope this helps,

Ala

On Thu, Oct 6, 2016 at 11:53 AM, Markus Stockh= au=3D sen <stoc= khause=3D n(a)collogia.de> wrote:

Hi Ala,

> Von: Adam Litke [alitke(a)redhat.com]
> Gesendet: Freitag, 30. September 2016 15:54
> An: Markus Stockhausen
> Cc: Ovirt Users; Ala Hino; Nir Soffer
> Betreff: Re: [ovirt-users] Cleanup illegal snapshot
>
> On 30/09/16 05:47 +0000, Markus Stockhausen wrote:
> >Hi,
> >
> >if a OVirt snapshot is illegal we might have 2 situations.
> >
> >1) qemu is still using it - lsof shows qemu access to the base raw= =3D and the
> >delta qcow2 file. -> E.g. a previous live merge failed. In the = =3D past we
> >successfully solved that situation by setting the status of the de= =3D lta image
> >in the database to OK.
> >
> >2) qemu is no longer using it. lsof shows qemu access only to the = =3D the base
> >raw file -> E.g. a previous live merge succeded in qemu but Ovi= =3D rt did not
> >recognize.
> >
> >How to clean up the 2nd situation?
>
> It seems that you will have to first clean up the engine database to > remove references to the snapshot that no longer exists. Then yo= =3D u
> will need to remove the unused qcow2 volume.
>
> Unfortunately I cannot provide safe instructions for modifying the
> database but maybe Ala Hino (added to CC:) will be able to help with > that.

Do you have some tip for me?

>
> One you have fixed the DB you should be able to delete the volume
> using a vdsm verb on the SPM host:
>
> # vdsClient -s 0 deleteVolume <sdUUID> <spUUID> <imgUUI= =3D D> <volUUID>