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 30: | Line 30: | ||
file truncates), all the other containers I/O will block waiting | file truncates), all the other containers I/O will block waiting | ||
for the journal to be written to disk. In some extreme cases we saw | for the journal to be written to disk. In some extreme cases we saw | ||
− | up to 15 seconds of such blockage | + | up to 15 seconds of such blockage.</li> |
− | |||
<!--T:7--> | <!--T:7--> | ||
Line 40: | Line 39: | ||
<!--T:8--> | <!--T:8--> | ||
<li>Since many containers share the same file system, and the number | <li>Since many containers share the same file system, and the number | ||
− | of inodes on a file system is limited [ | + | of inodes on a file system is limited [for most file systems], vzquota |
should also be able to limit inodes on a per container (per directory) | should also be able to limit inodes on a per container (per directory) | ||
basis.</li> | basis.</li> |