When dealing with migration of large OpenVZ containers (500-700GB) we noticed the vzquota takes very long time before the migrated container can start on the second node.
We tested using VZQUOTA=NO on a per-container configuration, it seems to work but no disk usage info are present on proxmox web interface for that container.
There is some workaround I'm missing to obtain both fast container start and keeping container disk usage info ?
Andrea
We tested using VZQUOTA=NO on a per-container configuration, it seems to work but no disk usage info are present on proxmox web interface for that container.
There is some workaround I'm missing to obtain both fast container start and keeping container disk usage info ?
Andrea