<p dir="ltr"><br>
On Oct 24, 2014 5:33 PM, "Devon B." <<a href="mailto:devon.b@virtualcomplete.com">devon.b@virtualcomplete.com</a>> wrote:<br>
><br>
> I think what Kir was getting at was set the diskinodes equal to 65536 x GiB before converting. So for 40GiB, set diskinodes to 2621440</p>
<p dir="ltr">Either that, or just remove the DISKINODES from CT config <br></p>
<p dir="ltr">> On 10/24/2014 8:05 PM, Nick Knutov wrote:<br>
>><br>
>> Thanks, now I understand why this occurred, but what is the easiest way<br>
>> to convert a lot of different CTs to ploop? As I remember there is no<br>
>> way to set up unlimited diskinodes or disable them (in case I want to<br>
>> use CT size when converting to ploop and don't want to think about<br>
>> inodes at all).<br>
>><br>
>><br>
>> 25.10.2014 5:31, Kir Kolyshkin пишет:<br>
>>><br>
>>> [...]<br>
>>> Previously, we didn't support setting diskinodes for ploop, but later we<br>
>>> found<br>
>>> a way to implement it (NOTE: for vzctl create and vzctl convert only).<br>
>>> The trick we use it we create a file system big enough to accomodate the<br>
>>> requested number of inodes, and then use ploop resize (in this case<br>
>>> downsize)<br>
>>> to bring it down to requested amount.<br>
>>><br>
>>> In this case, 1G inodes requirements leads to creation of 16TB filesystem<br>
>>> (remember, 1 inode per 16K). Unfortunately, such huge FS can't be downsized<br>
>>> to as low as 40G, the minimum seems to be around 240G (values printed in<br>
>>> the error message are in sectors which are 512 bytes each).<br>
>>><br>
>>> Solution: please be reasonable when requesting diskinodes for ploop.<br>
>><br>
>><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@openvz.org">Users@openvz.org</a><br>
> <a href="https://lists.openvz.org/mailman/listinfo/users">https://lists.openvz.org/mailman/listinfo/users</a><br>
</p>