1,734
edits
Changes
Marked this version for translation
<translate>
<!--T:1-->
[[Ploop]] images has the following limits:
<!--T:2-->
* Number of snapshots: 126
* Image size:
* Inner ext4 file system size: currently set to 16 TB
== Conversion ==<!--T:3-->
<!--T:4-->
Use ploop convert tool to convert from ploop v1 to ploop v2 image.
== Internals == <!--T:5-->
== Internals =Image size limit === <!--T:6-->
<!--T:7-->
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
number of sectors is (u32)-12<sup>32</sup>, which is 4294967295. As sector size is 512 bytes,4294967295 sectors are equal to 2 terabytes. From that numberAs the first megabyte of the image isused 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.Block size itself is measured in 512 byte sectors, we should subtractand can be specified during image creation.If not specified, block size defaults to 2048 sectors, i.e. 1 megabyte. Therefore, the image can be up to 4 petabytes (4096 TB) in size.Same as with ploop v1, the first 1MB megabyte of the image is used for header and L2 translation table, maximum image size is decreased by 1MB. === Filesystem size limit === <!--T:9--> <!--T:10-->Currently ext4 file system is used. An ability to resize ext4 is limited byits block group descriptor table, which size can be specified during filesystem creation time, using <code>-Eresize</code> option to mke2fs.Currently ploop library hardcodes this value so that filesystem can be resizedup to 16 TB of space.</translate>