• Article for your preferred language does not exist. Below is international version of the article.

Article ID: 114957, created on Oct 16, 2012, last review on Jun 17, 2016

  • Applies to:
  • Odin Business Automation Standard 4.5
  • Virtuozzo 6.0
  • Virtuozzo containers for Linux 4.7


It is not possible to start a ploop-based container on Parallels Cloud Server 6.0 with the following error:

~# vzctl start 100
add delta dev=/dev/ploop1 img=/vz/private/100/root.hdd/root.hds (rw)
Mounting /dev/ploop1p1 at /vz/root/100 fstype=ext4 data='balloon_ino=12,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,pfcache_csum,pfcache=/vz/pfcache'
Container is mounted
Starting the Container ...
Setting permissions 20002 dev 0x7d00
Adding offline management to Container(1): 4643 8443 4649
Adding IP addresses:
Setting permissions 60010 dev 0xb611
Old quota version detected Quota utilities version 3.13. Quota should be > 3.16
Error setting up ugid quota
Unmounting file system at /vz/root/100
Unmounting device /dev/ploop1
Container is unmounted
Failed to start the Container


As of Parallels Cloud Server 6.0, containers are using new layout and filesystem inside containers is Ext4. Some old distributions like CentOS 5, RHEL 5, Debian 5 have the outdated quota tool (<3.16) which does not recognize Ext4 filesystem, thus if the container has second level quota limit (quotaugidlimit) set, then the quotacheck command invocation fails.


The issue is permanently fixed in Parallels Cloud Server 6 update 3:

116301 Parallels Cloud Server 6.0 Update 3 Hotfix 1 (6.0.0-1323)

After installing the update disable journal quota for already existing containers which have the problem:

~# vzctl set CTID --jquota no --save

For older versions of the product it is possible to disable second-level quota inside the containers:

~# prlctl set CTID --quotaugidlimit 0

Search Words

unable to start ct

Old quota version detected

high load

error starting container

Quota should be > 3.16

Error setting up ugid quota

Quota utilities version 3.13

unable to start after migrate to ploop

0dd5b9380c7d4884d77587f3eb0fa8ef 2897d76d56d2010f4e3a28f864d69223 c62e8726973f80975db0531f1ed5c6a2 e8e50b42231236b82df27684e7ec0beb d02f9caf3e11b191a38179103495106f 0c05f0c76fec3dd785e9feafce1099a9 400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 624ca542e40215e6f1d39170d8e7ec75 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF