Solus
SolusVM Technical Questions
OpenVZ

Why it is not possible to set a disk size more than 16TB for OpenVZ container in SolusVM

Updated March 21, 2023 19:45

Ivan Bezuglov

Have more questions? Submit a request

Applicable to:

SolusVM

Question

Why it is not possible to set a disk size more than 16TB for OpenVZ container in SolusVM?

Answer

This limitation comes from OpenVZ and ploop file system layout itself:

CONFIG_TEXT: Currently ext4 file system is used. An ability to resize ext4 is limited by its block group descriptor table, which size can be specified during file system creation time, using -Eresize option to mke2fs. Currently ploop library hardcodes this value so that filesystem can be resized up to 16 TB of space

Refer OpenVZ Wiki for more information about ploop limitations

Articles in this section

How to migrate VPSes from the old SolusVM master with OpenVZ 6 to the new SolusVM master with OpenVZ 7?
Cannot start OpenVZ container: Unable to apply new quota values: ugid quota not initialized
OpenVZ container cannot start on the SolusVM slave node: e2fsck failed (exit code 4)
Does SolusVM support OpenVZ hardware virtualization for VPSes?
Why it is not possible to set a disk size more than 16TB for OpenVZ container in SolusVM
How to add OpenVZ templates to the SolusVM?
Unable to create OpenVZ VM: Status Offline
Hostname reset issue after the Reboot-OpenVZ VPS: hostname is changed to a non-FQDN
Incorrect RAM value for OpenVZ VPS
How to create a template in OpenVZ Virtuozzo 7 using standard(legacy) OpenVZ 6 template to use in SolusVM?

Comments

0 comments

Please sign in to leave a comment.