Editing Ploop/Why
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 134: | Line 134: | ||
<!--T:27--> | <!--T:27--> | ||
− | * File system journal is not bottleneck anymore | + | * 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 | * 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 need for per-directory quotas | * Disk space quota can be implemented based on virtual device sizes; no need for per-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) | + | * 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 backup is easy and consistent | ||
* Live migration is reliable and efficient | * Live migration is reliable and efficient | ||
Line 144: | Line 144: | ||
<!--T:28--> | <!--T:28--> | ||
In addition: | In addition: | ||
+ | * Efficient container creation | ||
* [Potential] support for QCOW2 and other image formats | * [Potential] support for QCOW2 and other image formats | ||
* Support for different storage types | * Support for different storage types |