Hi,
I've been facing this odd error in the past day, with
> Unable to clone: Too many open files
The containers just stop and do not start up again,
currently running kernel 3.10.0-957.27.2.vz7.107.4
I've checked this out on google and wasn't able to find much on it, any
help would be appreciat
Hi
I've been trying to repair this ploop image
[root@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=1887
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 rašė:
> Hi
> I'
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
wrote:
> I think this is a bug in the newest released ploop packag
So the fix for this involves, scp the private folder + image
(root.hdd/hdds, DiskDescriptor.xml etc) to a OpenVZ 6 based node
Then running ploop balloon discard,
ploop balloon discard --automount /vz/private
/$CT/root.hdd/DiskDescriptor.xml
Then scp the image back to the OpenVZ 7 based node into
