Article ID: 117618, created on Sep 30, 2013, last review on May 11, 2014

  • Applies to:
  • Virtuozzo


Command "vzstat -b" displays [CRIT] mark in front of "Disk" :

Disks [CRIT]: in 0.131MB/s, out 11.610MB/s


Pressing "v" button will provide a verbose output, which will reveal why disk is marked as "CRIT":

    Disks [CRIT]: in 0.131MB/s, out 11.610MB/s
      sda3(/) free: 113980MB(97%), 7534362ino(99%)
      sda1(/boot) free: 548MB(92%), 38356ino(99%)
      sdb1(/vz) free: 6722519MB(89%), 487138699ino(99%)
      ploop31695p1(/vz/pfcache) free: 9908MB(98%), 655296ino(99%)
      ploop26772p1(/vz/root/7711119) free: 37MB(3%), 632593ino(96%)

In the output listed above we can see that disk /dev/ploop26772p1 (/vz/root/7711119) is almost out of free space:

    ~# vzquota stat 7711119
       resource          usage       softlimit      hardlimit
      1k-blocks         946052         984368         984368
         inodes          22767         655360         655360


According to provided path (/vz/root/7711119) we can tell that device belongs to container 7711119. Increasing it's diskspace will solve the issue:

    ~# vzctl set 7711119 --diskspace 1984368:2000000 --save

Search Words


Disk [CRIT]



0dd5b9380c7d4884d77587f3eb0fa8ef 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF