Article ID: 111935, created on Aug 17, 2011, last review on May 8, 2014

  • Applies to:
  • Virtuozzo containers for Linux 4.7

Symptoms

After the quota is reinitialized on a newly created container, its usage is shown as not consistent.
[root@vtd-wst ~]# vzctl create 200 --ostemplate redhat-el6-x86 
Creating Container private area (redhat-el6-x86) 
Container is mounted 
Postcreate actions performed 
Container is unmounted 
Container private area was created 
[root@vtd-wst ~]# 
 
 
[root@vtd-wst ~]# vzquota show 200 
          resource   usage   softlimit   hardlimit   grace
	 1k-blocks   36168    2097152     2306048
	  inodes      5906    200000      220000
 
Re-init quota: 
[root@vtd-wst ~]# vzquota drop 200 
[root@vtd-wst ~]# vzctl quotainit 200 

 
[root@vtd-wst ~]# vzquota show 200 
         resource   usage   softlimit  hardlimit grace
	1k-blocks   36176    2097152    2306048
	  inodes     5908    200000     22000
        

Resolution

Create the containers in the old layout.
 
[root@ts91 ~]# ls -la /vzt/private/200/ 
total 24 
drwx------ 6 root root 4096 Jul 12 13:49 . 
drwxr-xr-x 24 root root 4096 Jul 12 13:49 .. 
drwxrwxrwx 2 root root 4096 Jul 12 12:59 cow 
dr-sr-xr-x 20 root root 4096 Jul 12 13:04 root 
drwxr-xr-x 3 root root 4096 Jul 12 13:04 templates 
lrwxrwxrwx 1 root root 7 Jul 12 12:59 VERSION -> 005.004 
drwxr-xr-x 2 root root 4096 Jul 12 13:49 .vza 

[root@ts91 ~]# grep LAY /etc/vz/vz.conf 
VELAYOUT=3 


 Because the quota is enabled for $VE_PRIVATE for the old layout, it cannot be fixed.

0c05f0c76fec3dd785e9feafce1099a9 d02f9caf3e11b191a38179103495106f e8e50b42231236b82df27684e7ec0beb 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF