There is a difference in free disk space size for ploop OpenVZ containers in SolusVM UI and output of df -h command

Symptoms 

There is a difference in free disk space size for ploop OpenVZ containers in SolusVM UI and output of df -h command 

Cause

Such behaviour caused by SolusVM bug #SVM-2101 It considered to be fixed in future release

Resolution

Note: The issue persists for the containers that has ploop file system layout. For simfs containers it works as expected.

There is not workaround at the moment.

Here is more details about this behavior. SolusVM calculates the free diskspace for the containers with a ploop layout as below:

CONFIG_TEXT: total_space - used_space

total_space is a value from the database
used_space is the output of the following command:

# vzlist CTID -H -o diskspace | awk '\{print $1}

Output of the 'df -h' shows available disk space that is lesser than in SolusVM, because part of the space is being reserved by system, like tmpfs partition