Hi,
I tried unlock_entity.sh, and it solved the issue. So far so good.

But it's still unclear why disks were locked.

Let me make an hypothesis: in ovirt 4.3 a failure in snapshot removal
would lead to a snapshot in illegal status. No problem, you can remove
again and the situation is fixed.
In ovirt 4.4 a failure in snapshot removal leave the whole disk in
locked state (maybe a bug?), preventing any further action.

Does it make sense?


On 03/02/2021 12:25, Giulio Casella wrote:
> Hi Shani,
> no tasks listed in UI, and now "taskcleaner.sh -o" reports no task (just
> before I gave "taskcleaner.sh -r").
> But disks are still locked, and "unlock_entity.sh -q -t all -c"
> (accordingly) reports only two disk's uuid (with their vm's uuid).
>
> Time to give a chance to unlock_entity.sh?
>
> Regards,
> gc
>
> On 03/02/2021 11:52, Shani Leviim wrote:
>> Hi Giulio,
>> Before running unlock_entity.sh, let's try to find if there's any task
>> in progress.
>> Is there any hint on the events in the UI?
>> Or try to run [1]:
>> ./taskcleaner.sh -o  
>>
>> Also, you can verify what entities are locked [2]:
>> ./unlock_entity.sh -q -t all -c
>>
>> [1]
>> https://github.com/oVirt/ovirt-engine/blob/master/packaging/setup/dbutils/taskcleaner.sh
>> <https://github.com/oVirt/ovirt-engine/blob/master/packaging/setup/dbutils/taskcleaner.sh>
>> [2]
>> https://github.com/oVirt/ovirt-engine/blob/master/packaging/setup/dbutils/unlock_entity.sh
>> <https://github.com/oVirt/ovirt-engine/blob/master/packaging/setup/dbutils/unlock_entity.sh>
>>
>> *Regards,
>> *
>> *Shani Leviim
>> *
>>
>>
>> On Wed, Feb 3, 2021 at 10:43 AM Giulio Casella <giulio@di.unimi.it
>> <mailto:giulio@di.unimi.it>> wrote:
>>
>>     Since yesterday I found a couple VMs with locked disk. I don't know the
>>     reason, I suspect some interaction made by our backup system (vprotect,
>>     snapshot based), despite it's working for more than a year.
>>
>>     I'd give a chance to unlock_entity.sh script, but it reports:
>>
>>     CAUTION, this operation may lead to data corruption and should be used
>>     with care. Please contact support prior to running this command
>>
>>     Do you think I should trust? Is it safe? VMs are in production...
>>
>>     My manager is 4.4.4.7-1.el8 (CentOS stream 8), hosts are oVirt Node
>>     4.4.4
>>
>>
>>     TIA,
>>     Giulio
>>     _______________________________________________
>>     Users mailing list -- users@ovirt.org <mailto:users@ovirt.org>
>>     To unsubscribe send an email to users-leave@ovirt.org
>>     <mailto:users-leave@ovirt.org>
>>     Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>     <https://www.ovirt.org/privacy-policy.html>
>>     oVirt Code of Conduct:
>>     https://www.ovirt.org/community/about/community-guidelines/
>>     <https://www.ovirt.org/community/about/community-guidelines/>
>>     List Archives:
>>     https://lists.ovirt.org/archives/list/users@ovirt.org/message/M4HYMDMHOKC5DCHDP6CFLM4RWJQNN7R4/
>>     <https://lists.ovirt.org/archives/list/users@ovirt.org/message/M4HYMDMHOKC5DCHDP6CFLM4RWJQNN7R4/>
>>
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-leave@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/FEXMZKZFYCWUOVZXZ3C3XZ7VBVYKFJGH/
>

o