Re: [Users] Ploop filesystem provisioned incorrectly (wrong size)

2014-07-29 Thread Kir Kolyshkin
On 07/26/2014 08:50 PM, Kir Kolyshkin wrote: On 07/26/2014 12:45 PM, Kevin Holly wrote: On 23/07/14 09:34, Kir Kolyshkin wrote: I just talked with a L3 Supporter of SolusVM and they told me that this seems to be a well known vzctl bug. Great, can they point out to a bug in

Re: [Users] Ploop filesystem provisioned incorrectly (wrong size)

2014-07-26 Thread Kevin Holly
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/07/14 09:34, Kir Kolyshkin wrote: I just talked with a L3 Supporter of SolusVM and they told me that this seems to be a well known vzctl bug. What SolusVM basically does is this on creation of the container:

Re: [Users] Ploop filesystem provisioned incorrectly (wrong size)

2014-07-26 Thread Kevin Holly
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26/07/14 21:45, Kevin Holly wrote: Oh, and downgrading vzctl to version vzctl-4.6.1-1.x86_64 helped for now... - -- Best regards Kevin Holly - r...@hallowe.lt - http://hallowe.lt/ -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using

Re: [Users] Ploop filesystem provisioned incorrectly (wrong size)

2014-07-26 Thread Kir Kolyshkin
On 07/26/2014 12:45 PM, Kevin Holly wrote: On 23/07/14 09:34, Kir Kolyshkin wrote: I just talked with a L3 Supporter of SolusVM and they told me that this seems to be a well known vzctl bug. Great, can they point out to a bug in bugzilla.openvz.org? What SolusVM basically does is this on

Re: [Users] Ploop filesystem provisioned incorrectly (wrong size)

2014-07-26 Thread Kir Kolyshkin
On 07/26/2014 01:31 PM, Kevin Holly wrote: On 26/07/14 21:45, Kevin Holly wrote: Oh, and downgrading vzctl to version vzctl-4.6.1-1.x86_64 helped for now... For the exact reason I explained in the previous email -- it just ignores diskinodes. Not sure why SolusVM guys can't figure it out (or

Re: [Users] Ploop filesystem provisioned incorrectly (wrong size)

2014-07-23 Thread Kevin Holly
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Kir, On 23/07/14 00:25, Kir Kolyshkin wrote: I failed to reproduce your problem locally: Okay, then I have to dig further and see where the problem is. Final question, just curious -- are you paying to SolusVM? If yes, why don't you use their

Re: [Users] Ploop filesystem provisioned incorrectly (wrong size)

2014-07-22 Thread Kevin Holly
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi again, I just tried to reinstall this container... The log of that can be found here: https://ezcrypt.it/Hd9n#SiP14ajsc8sV0SLiGm1diEc1 There is not much difference with the ploop filesystem now. Same size (2TB but only 219GiB/235GB available) and

Re: [Users] Ploop filesystem provisioned incorrectly (wrong size)

2014-07-22 Thread Kir Kolyshkin
On 07/22/2014 02:44 PM, Kevin Holly wrote: Hi again, I just tried to reinstall this container... The log of that can be found here: https://ezcrypt.it/Hd9n#SiP14ajsc8sV0SLiGm1diEc1 The only strange thing I see is Killing container, perhaps you use an incorrect sequence for vzctl set