Hi,
I think we should treat each problem separately:
Can you run that SQL query on your engine and see the output?
SELECT *
FROM images_storage_domain_view images_storage_domain_view
WHERE image_group_id = '55893adf-1e56-4346-8070-4b3e660dd44d';
and same for 825765ba-b132-4b36-8cb9-8ecd2c7b597a.
Let's first verify the engine and vdsm are synced,
According to the vdsm-tool dump-volume-chains,
the disk you've mentioned seems to be legal:
image: a0f9a434-7837-4ec6-8017-c9698ed5cd01
- 64ac336f-25d8-43d0-aeb8-7fb77bf6ef97
status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
type: PREALLOCATED, capacity: 214748364800, truesize: 214748364800
Please share the output of the SQL query for this image as well
(a0f9a434-7837-4ec6-8017-c9698ed5cd01)
Also, can you please share a screenshot of the snapshot's deletion and the
illegal images?
*Regards,*
*Shani Leviim*
On Mon, Oct 19, 2020 at 6:46 PM Massimo Mad <mad196...@gmail.com> wrote:
> Hi,
> It's very strange because in the engine UI i have only one disk in illegal
> status.
> But i have a problem with another VM that have all the disk OK the storage
> migration begins, takes the snap shot then fails and the snapshot is
> deleted.
> the size of the vm with the disk in illega is 200Gb the id of the disk is
> a0f9a434-7837-4ec6-8017-c9698ed5cd01
> Regards
> Massimo
>
>
> Il giorno lun 19 ott 2020 alle ore 15:47 Shani Leviim <slev...@redhat.com>
> ha scritto:
>
>> Hi Massimo,
>> As shown on the output, you currently have 2 illeagal images:
>>
>> image: 55893adf-1e56-4346-8070-4b3e660dd44d
>>
>> - ea57d10b-13d5-4696-bedc-13a92b88f32d
>> status: ILLEGAL, voltype: LEAF, format: COW, legality:
>> *ILLEGAL*, type: SPARSE, capacity: 107374182400, truesize: 1744830464
>>
>>
>> image: 825765ba-b132-4b36-8cb9-8ecd2c7b597a
>>
>> - 5c534181-fbd6-4912-afdc-4ac812e0e9fe
>> status: ILLEGAL, voltype: LEAF, format: COW, legality:
>> *ILLEGAL*, type: SPARSE, capacity: 85899345920, truesize: 1879048192
>>
>> Can you try removing them from the engine UI?
>>
>>
>> *Regards,*
>>
>> *Shani Leviim*
>>
>>
>> On Mon, Oct 19, 2020 at 4:36 PM Massimo Mad <mad196...@gmail.com> wrote:
>>
>>> Hi Shani
>>> I run the command on the host owner of the SPM it's correct ?
>>> This is the output:
>>> [root@ovirthpr01 ~]# vdsm-tool dump-volume-chains
>>> eb483eb3-a9ce-4867-9ce8-96a0ca171042
>>>
>>> Images volume chains (base volume first)
>>>
>>> image: ff44dc13-de50-4891-84ce-9fb3e3fe1c88
>>>
>>> - c45ee9cd-17e3-4cec-b7fb-74af27e792a8
>>> status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
>>> type: PREALLOCATED, capacity: 134217728, truesize: 134217728
>>>
>>>
>>> image: a0f9a434-7837-4ec6-8017-c9698ed5cd01
>>>
>>> - 64ac336f-25d8-43d0-aeb8-7fb77bf6ef97
>>> status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
>>> type: PREALLOCATED, capacity: 214748364800, truesize: 214748364800
>>>
>>>
>>> image: 4da04f46-2fea-436f-9648-772c24a849c3
>>>
>>> - 77ddb7b8-b10f-4d7e-82df-36e077a9eb25
>>> status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
>>> type: PREALLOCATED, capacity: 134217728, truesize: 134217728
>>>
>>>
>>> image: 55893adf-1e56-4346-8070-4b3e660dd44d
>>>
>>> - ea57d10b-13d5-4696-bedc-13a92b88f32d
>>> status: ILLEGAL, voltype: LEAF, format: COW, legality:
>>> ILLEGAL, type: SPARSE, capacity: 107374182400, truesize: 1744830464
>>>
>>>
>>> image: 825765ba-b132-4b36-8cb9-8ecd2c7b597a
>>>
>>> - 5c534181-fbd6-4912-afdc-4ac812e0e9fe
>>> status: ILLEGAL, voltype: LEAF, format: COW, legality:
>>> ILLEGAL, type: SPARSE, capacity: 85899345920, truesize: 1879048192
>>>
>>>
>>> image: 0264f52e-fa59-4523-81e4-47564193665e
>>>
>>> - dfb3d366-f2d3-49ee-8ca3-3b44e24a0111
>>> status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
>>> type: PREALLOCATED, capacity: 536870912000, truesize: 536870912000
>>> And after what is the next step?
>>> Regards
>>> Massimo
>>>
>>>
>>> Il giorno lun 19 ott 2020 alle ore 13:51 Shani Leviim <
>>> slev...@redhat.com> ha scritto:
>>>
>>>> Hi Massimo,
>>>> In order to locate the illegal image, you can run this command on the
>>>> host:
>>>> vdsm-tool dump-volume-chains <sd_id>
>>>>
>>>> It's also recommended to verify that the engine and vdsm are synced
>>>> about that image, once you've find it, by running this command on the
>>>> engine:
>>>> SELECT *
>>>> FROM images_storage_domain_view images_storage_domain_view
>>>> WHERE image_group_id = <image_group_id>;
>>>>
>>>> Than, you can try removing it from the engine.
>>>> (and if it doesn't work - you can delete it from the DB)
>>>>
>>>>
>>>> *Regards,*
>>>>
>>>> *Shani Leviim*
>>>>
>>>>
>>>> On Mon, Oct 19, 2020 at 11:15 AM Massimo Mad <mad196...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>> I try to delete a snapshot that i have created in the past, now in the
>>>>> events i have the following error:
>>>>> Failed to delete snapshot
>>>>> And the VM now has the exclamation point with the following message:
>>>>> VM has snapshot with disk in illegal status
>>>>> How i can fix this problem ?
>>>>> Regards
>>>>> Massimo
>>>>> _______________________________________________
>>>>> Users mailing list -- users@ovirt.org
>>>>> To unsubscribe send an email to users-le...@ovirt.org
>>>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>>>> oVirt Code of Conduct:
>>>>> https://www.ovirt.org/community/about/community-guidelines/
>>>>> List Archives:
>>>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/VZJ62WAKAVWWORPPEIKMAT4KXOB6AU2D/
>>>>>
>>>>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RRI5NQWIYRBBKC3XZUGZMC4C4VW2OK3F/
