rm /vz/lock/1200.lck
rm: remove regular file `/vz/lock/1200.lck'? y
vzctl start 1200
Container already locked
vzctl start 1200
Starting container ...
vzquota : (error) can't lock quota file, some quota operations are performing for id 1200
vzquota on failed [7]
vzquota off 1200
vzctl start 1200
vzquota on 1200
root@rttbox ~]# vzquota off 1200
vzquota : (error) Quota off syscall for id 1200: Device or resource busy
vzquota : (error) Possible reasons:
vzquota : (error) - Container's root is not unmounted
vzquota : (error) - there are opened files inside container's root/private area
vzquota : (error) - your current working directory is inside a container directory
vzquota : (error) root/private area
[root@rttbox ~]# vzctl start 1200
Container is already running
[root@rttbox ~]# vzquota on 1200
vzquota : (warning) Quota is running for id 1200 already
The above is what happens when everything is fine but it takes a long time for the quota update to complete, such after a live migration etc... you know it is often the case when the normal tricks don't work:
eg. removing the .lck file, turning quota on and off.
openvz, solutions, container, quota, operations, performing, rm, vz, lck, vzctl, vzquota, rttbox, syscall, resource, unmounted, directory, update, migration, etc, eg, removing,