Changes

Jump to: navigation, search

Ploop/Why

946 bytes added, 16:40, 5 August 2016
no edit summary
<ol>
<li>Since containers are living on one same file system, they all
share common properties of that file system (it's its type, block size,and other options). That means we can not cannot configure the above properties
on a per-container basis.</li>
* Support for different storage types
== Disadvantages == <!--T:29-->* Boot delays in each container after some restarts or in system crashs due the multiple forced FSCKs when using ext3/4 file systems* Container's starts fails when FSCK find several inconsistencies in FS needing manual intervention* Increased risks of unrecoverable errors due container crashes* Greatly increased risks of unrecoverable errors when used over a NFS due network instabilities* Extra IO use when shrinking a PLOOP due block re-alocation [varies due FS fragmentation]* Slight poor performance due additional PLOOP layers* Needs a manually defrag and compact operations to recover hardnode free space wasted by allocated and no-more used blocks in each container* Additional space wasted due the additional FS metadata and format* No support for hardnode bind mounts to other disks (like backups) [can be workarounded using "loopback" NFS-like solutions to hardnode but looses some performance] == See also == <!--T:2930-->
* [[Ploop]]
</translate>
[[Category: Storage]]
Anonymous user

Navigation menu