Thanks, now I understand why this occurred, but what is the easiest way to convert a lot of different CTs to ploop? As I remember there is no way to set up unlimited diskinodes or disable them (in case I want to use CT size when converting to ploop and don't want to think about inodes at all).
25.10.2014 5:31, Kir Kolyshkin пишет: > [...] > Previously, we didn't support setting diskinodes for ploop, but later we > found > a way to implement it (NOTE: for vzctl create and vzctl convert only). > The trick we use it we create a file system big enough to accomodate the > requested number of inodes, and then use ploop resize (in this case > downsize) > to bring it down to requested amount. > > In this case, 1G inodes requirements leads to creation of 16TB filesystem > (remember, 1 inode per 16K). Unfortunately, such huge FS can't be downsized > to as low as 40G, the minimum seems to be around 240G (values printed in > the error message are in sectors which are 512 bytes each). > > Solution: please be reasonable when requesting diskinodes for ploop. -- Best Regards, Nick Knutov _______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users