[Users] Issues after updating to 7.0.14 (136)

[Jehan PROCACCIA]

Hello 
thanks for the advices, I did disable onboot=yes => no , so that at next reboot my CTs don't start automatically and enter a dead lock/loop 
than I could restart manually my CTs 
In fact I discuss with devs , it seems I enter a dead lock when my centos8 CTs (using NFT / netfilter) stop/suspended when rebooting the HWNode 
they are looking a this potential issue with netflter and latest updates . 

to be continued ... 

Thanks . 


De: "Oleksiy Tkachenko" <mealexat at gmail.com> 
À: "OpenVZ users" <users at openvz.org> 
Envoyé: Mercredi 8 Juillet 2020 23:49:51 
Objet: Re: [Users] Issues after updating to 7.0.14 (136) 

>> ... 
>> Error in ploop_check (check.c:663): Dirty flag is set 
>> ... 
>> # ploop mount /vz/private/144dc737-b4e3-4c03-852c-25a6df06cee4/root.hdd/DiskDescriptor.xml 
>> Error in ploop_mount_image (ploop.c:2495): Image /vz/private/144dc737-b4e3-4c03-852c-25a6df06cee4/root.hdd/root.hds already used by device /dev/ploop11432 
>> ... 
>> 
>> I am lost , any help appreciated . 

I heard about 2 possible solutions: 
1. Reboot HW and stop CT. Then "ploop mount" CT's DiskDescriptor.xml for e2fsck. Unmount and restart CT. 
2. If won't help then create fresh new CT and move "broken" root.hds there. 

-- 
Oleksiy 

_______________________________________________ 
Users mailing list 
Users at openvz.org 
https://lists.openvz.org/mailman/listinfo/users 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/users/attachments/20200709/65876906/attachment.html>