Re: [Users] convert to ploop

2014-11-10 Thread Nick Knutov
Thanks, this is working.

For wiki - I did

find /etc/vz/conf/*.conf -type f -exec sed -i.bak
s/DISKINODES/#DISKINODES/g {} \;

VE=123 ; vzctl stop $VE ; vzctl convert $VE ; vzctl start $VE

Unfortunatly, I do not understand how to work with/edit MediaWiki and
I'm not sure on what page it's better to add this.

25.10.2014 7:32, Kirill Kolyshkin пишет:
 
 On Oct 24, 2014 5:33 PM, Devon B. devo...@virtualcomplete.com
 mailto:devo...@virtualcomplete.com wrote:

 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
 
 Either that, or just remove the DISKINODES from CT config
 
 On 10/24/2014 8:05 PM, Nick Knutov wrote:

 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.



 ___
 Users mailing list
 Users@openvz.org mailto:Users@openvz.org
 https://lists.openvz.org/mailman/listinfo/users
 
 
 
 ___
 Users mailing list
 Users@openvz.org
 https://lists.openvz.org/mailman/listinfo/users
 

-- 
Best Regards,
Nick Knutov
http://knutov.com
ICQ: 272873706
Voice: +7-904-84-23-130
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users


Re: [Users] convert to ploop

2014-11-10 Thread Kir Kolyshkin


On 11/10/2014 05:51 PM, Nick Knutov wrote:

Thanks, this is working.

For wiki - I did

find /etc/vz/conf/*.conf -type f -exec sed -i.bak
s/DISKINODES/#DISKINODES/g {} \;

VE=123 ; vzctl stop $VE ; vzctl convert $VE ; vzctl start $VE


By the way I just found it's enough to set DISKINODES to 0
(after stopping a container of course).



Unfortunatly, I do not understand how to work with/edit MediaWiki and
I'm not sure on what page it's better to add this.


I have modified this:

https://openvz.org/Ploop/Getting_started#Creating_a_new_CT,

and also wrote a whole new

https://openvz.org/Ploop/diskinodes

Hope it's enough information now.



25.10.2014 7:32, Kirill Kolyshkin пишет:

On Oct 24, 2014 5:33 PM, Devon B. devo...@virtualcomplete.com
mailto:devo...@virtualcomplete.com wrote:

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

Either that, or just remove the DISKINODES from CT config


On 10/24/2014 8:05 PM, Nick Knutov wrote:

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.



___
Users mailing list
Users@openvz.org mailto:Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users



___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users



___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users