Editing Ploop/Limits

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
 
<translate>
 
<translate>
<!--T:1-->
 
 
[[Ploop]] images has the following limits:
 
[[Ploop]] images has the following limits:
  
<!--T:2-->
 
 
* Number of snapshots: 126
 
* Number of snapshots: 126
 
* Image size:
 
* Image size:
Line 10: Line 8:
 
* Inner ext4 file system size: currently set to 16 TB
 
* Inner ext4 file system size: currently set to 16 TB
  
== Conversion == <!--T:3-->
+
== Conversion ==
  
<!--T:4-->
 
 
Use ploop convert tool to convert from ploop v1 to ploop v2 image.
 
Use ploop convert tool to convert from ploop v1 to ploop v2 image.
  
== Internals == <!--T:5-->
+
== Internals ==
  
=== Image size limit === <!--T:6-->
+
=== Image size limit ===
  
<!--T:7-->
 
 
Ploop v1 image size limitation comes from the fact that unsigned 32 bit integer
 
Ploop v1 image size limitation comes from the fact that unsigned 32 bit integer
 
is used to store sector address inside the ploop image. Therefore the maximum
 
is used to store sector address inside the ploop image. Therefore the maximum
Line 26: Line 22:
 
used for header and L2 translation table, maximum image size is decreased by 1MB.
 
used for header and L2 translation table, maximum image size is decreased by 1MB.
  
<!--T:8-->
 
 
Ploop v2 uses the same unsigned 32 bit field to address blocks rather than sectors.
 
Ploop v2 uses the same unsigned 32 bit field to address blocks rather than sectors.
 
Block size itself is measured in 512 byte sectors, and can be specified during image creation.
 
Block size itself is measured in 512 byte sectors, and can be specified during image creation.
Line 34: Line 29:
 
used for header and L2 translation table, maximum image size is decreased by 1MB.
 
used for header and L2 translation table, maximum image size is decreased by 1MB.
  
=== Filesystem size limit === <!--T:9-->
+
=== Filesystem size limit ===
  
<!--T:10-->
 
 
Currently ext4 file system is used. An ability to resize ext4 is limited by
 
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
 
its block group descriptor table, which size can be specified during file

Please note that all contributions to OpenVZ Virtuozzo Containers Wiki may be edited, altered, or removed by other contributors. If you don't want your writing to be edited mercilessly, then don't submit it here.
If you are going to add external links to an article, read the External links policy first!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)