Repairing wrongly reported quota by openVZ container

From Notes_Wiki
Revision as of 05:13, 18 March 2014 by Saurabh (talk | contribs)

<yambe:breadcrumb>Troubleshooting_openVZ_issues|Troubleshooting openVZ issues</yambe:breadcrumb>

Repairing wrongly reported quota by openVZ container

It is possible that a openVZ container shows incorrect usage when "df -h" is used inside container. To verify actual usage one can use: 

du -sh /vz/private/<CTID>

and compare the output with "df -h" used space output. If the values are incorrect then one can use following steps to get correct quota: 

 vzquota drop 161
 vzctl set <CTID> --diskspace <soft-limit>:<hard-limit> --save
 vzctl set <CTID> --diskinodes <soft-limit>:<hard-limit> --save
 vzctl set <CTID> --diskquota yes --save
 vzctl restart <CTID>


Note that if the used space is reported as 0 instead of a wrong value then it is possible that quota is not supported for the filesystem used by /vz. Check http://wiki.openvz.org/FAQ#What_filesystems_should_I_choose_for_saving_my_containers.3F for list of supported file-systems.

Retrieved from "http://www.sbarjatiya.com/notes_wiki/index.php?title=Repairing_wrongly_reported_quota_by_openVZ_container&oldid=1548"