[Users] Repairing a ploop image

[Arjit Chaudhary]

Seems like someone had this issue earlier too,
https://lists.openvz.org/pipermail/users/2017-August/007361.html

even the compact utility with --automount doesnt help in this case

On Fri, Jan 3, 2020 at 9:30 PM Skirmantas Juraška <s.juraska at gmail.com>
wrote:

> I think this is a bug in the newest released ploop package version. I have
> opened a bug report but no one is paying attention. You can try to
> downgrade the ploop package or move this container (ploop) to the older
> node. Container should work.
>
> 2020-01-03, pn, 17:36 Arjit Chaudhary <arjit.c at gmail.com> rašė:
>
>> Hi
>> I've been trying to repair this ploop image
>>
>> [root at internal ~]# ploop check -F /vz/private/102/root.hdd/root.hds
>> Reopen rw /vz/private/102/root.hdd/root.hds
>> Opening delta /vz/private/102/root.hdd/root.hds
>> Error in range_build_rmap (balloon_util.c:542): Image corrupted: L2[38]
>> == 155797 (max=188741632) (2)
>>
>> I can't seem to find any message / information about fixing " Error in
>> range_build_rmap " on google either, is this a non-recoverable image ?
>>
>> --
>> Thanks,
>> Arjit Chaudhary
>> _______________________________________________
>> Users mailing list
>> Users at openvz.org
>> https://lists.openvz.org/mailman/listinfo/users
>>
> _______________________________________________
> Users mailing list
> Users at openvz.org
> https://lists.openvz.org/mailman/listinfo/users
>


-- 
Thanks,
Arjit Chaudhary
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/users/attachments/20200104/335d5bba/attachment-0001.html>