SymptomsIt is not possible to start a ploop-based container on Parallels Cloud Server 6.0 with the following error:
[root@mypcs ~]# 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
CauseAs of Parallels Cloud Server 6.0 containers are using new layout and filesystem inside containers is ext4.
Some 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 the quotacheck command invocation will fail.
It is suggested to use recent versions of distributions which support modern filesystem types: CentOS 6, RHEL 6 and Debian 6.
Otherwise it is possible to disable second-level quota inside the containers:
~# prlctl set 100 --quotaugidlimit 0