6,534
edits
Changes
more about vzquota and simfs
up to 15 seconds of such blockage.</li>
<li>There is no such thing as a per-directory disk quota for LinuxSince many containers share the same file system with limited space,so in order to limit containers disk space we had to develop oneper-directorydisk quotas (i.e. vzquota).</li> <li>Since many containers share the same file system, and the numberof inodes on a file system is limited [for most file systems],vzquotashould also be able to limit inodes on a per container (per directory) it's basis.</li> <li>In order for in-container (aka second-level) disk quota(i.e. standard per-user and per-group UNIX dist quota) to work,we had to provide a dummy file system called vzquotasimfs. Its solepurpose is to have a superblock which is needed for disk quotato work.</li>
<li>When doing a live migration without some sort of shared storage
* File system journal is not bottleneck anymore
* Large-size image files I/O instead of lots of small-size files I/O on management operations
* Disk space quota can be implemented based on virtual device sizes. No ; no need for subper-tree directory quotas* Number of inodes doesn't have to be limited because this is not a shared resource anymore (each CT has its own file system)
* Live backup is easy and consistent
* Live migration is reliable and efficient
* Different containers may use file systems of different types and properties
In addition: