How to speed up or avoid "vzquota recalculating disk usage"

[kotakomputer]

I have Proxmox Server with 25 CT (OpenVZ). When server restart, I got:
-------------------------
Starting container ...
vzquota : (warning) Incorrect quota shutdown for id 107, recalculating disk usage
-------------------------

This take time a lot, 1 CT spend 30-120 minutes to live.
How to automatically avoid this recalculating, or any idea to speed up this process?

 

[dietmar]

How did you shutdown CT 107? (That should not happen if you cleanly shutdown the CT).

 

[kotakomputer]

The shutdown process is not normal, such as UPS failure or by pressing RESET button. My point is to speed up or better avoid this recalculating process. Any idea? Because on a CT which contains 125 user accounts, this process can take 2 hours!

 

[dietmar]

The shutdown process is not normal, such as UPS failure or by pressing RESET button.

Maybe you need faster disks?

 

[kobuki]

The shutdown process is not normal, such as UPS failure or by pressing RESET button. My point is to speed up or better avoid this recalculating process. Any idea? Because on a CT which contains 125 user accounts, this process can take 2 hours!

I'd suggest 2 things:
- Always ensure a clean shutdown of the CT/HN.
- Use bind mounts to attach a separate directory containing the bulk of the data. That way you can keep the CT size minimal and can deal with potential disk problems outside of the CT. Naturally this would change the way you use quotas (if you use any). See http://wiki.openvz.org/Bind_mounts

 

[kotakomputer]

After reading OpenVZ manual then I found the solution:

Open /etc/vz/vz.conf

VZFASTBOOT=no

Change to:

VZFASTBOOT=yes

# /etc/init.d/vz restart

 

[SamTzu]

Using journaling ext4 filesystem on "second" hard drive dedicated to data storage speeds up the process quite a lot.

The quota option actually only enables second level quota.
So it only affects the VPS if it can use quota or not.

An example:
Mailbox name@company.tld has a 10MB Mailbox

This would no longer be possible without second level quota.

 

[SamTzu]

It does seem that the "quota" settings are not being honored in Proxmox 3.3-5.
Even if I disable the quota on OpenVZ container and add fastboot manually the container will be force recalculated on VPS start up.

vzquota : (warning) Incorrect quota shutdown for id 100, recalculating disk usage