Article ID: 123812, created on Dec 6, 2014, last review on May 26, 2015

  • Applies to:
  • Virtuozzo 6.0


A ploop-based container cannot be resized with a following error:

~# vzctl set 101 --diskspace 250G --save
Resize the image /vz/private/101/root.hdd to 262144000K
dumpe2fs 1.41.12 (17-May-2010)
Failed to resize image /vz/private/101/root.hdd: Unable to change image size to 524279808 sectors, minimal size is 795978752
Saved parameters for Container 101

However, real consumption is less than 250G:

~#vzctl exec 101 df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/ploop42782p1     196G  125G   48G  73% /
tmpfs                 1.0G     0  1.0G   0% /lib/init/rw
tmpfs                 1.0G     0  1.0G   0% /dev/shm

Container may have a huge balloon:

~# ploop-balloon show -m /vz/root/101/
Current size of hidden balloon is 69986156544 bytes


One of the possible reasons is that the container had its diskspace limit set to a significantly greater value than it is right now, or converted from VZFS to ploop, and source container had relatively high diskinodes limit. Such containers have filesystem with a huge space reserved for inodes table, e.g. container with 5 Tb diskspace limit will have ~70Gb reserved for the inodes table.


To resolve the issue offline resize should be performed.

  1. Stop the container:

    ~# vzctl stop 101
  2. Resize the container in offline mode:

    ~# vzctl set 101 --diskspace 250G --save --offline

NOTE: At least the same amount of space consumed by the container should be free on the node to perform offline resize operation.

Search Words

balloon size

Unable to change image size

resize ploop

c62e8726973f80975db0531f1ed5c6a2 2897d76d56d2010f4e3a28f864d69223 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF