Difference between revisions of "Repairing wrongly reported quota by openVZ container"
From Notes_Wiki
(Created page with "<yambe:breadcrumb>Troubleshooting_openVZ_issues|Troubleshooting openVZ issues</yambe:breadcrumb> =Repairing wrongly reported quota by openVZ container= It is possible that a ...") |
(No difference)
|
Revision as of 10:36, 23 June 2013
<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>
