-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:
-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
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
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
