vzquota : (error) Quota on syscall for xxx: Device or resource busy
Posted by Category: VPS ManagementYou may receive the following error message while starting a VPS:
root@server [~]# vzctl start VEID
vzquota : (error) Quota on syscall for id xxx: Device or resource busy
vzquota : (error) Possible reasons:
vzquota : (error) – Container’s root is already mounted
vzquota : (error) – there are opened files inside Container’s private area
vzquota : (error) – your current working directory is inside Container’s private area
vzquota : (error) Use -v option to see currently opened file(s).
Running vzquota on failed for Container xxx
The error message indicates 2 things:
1) There are some files in open state inside the VPS private area. You can check if there are any open files by executing:
lsof 2> /dev/null | egrep ‘/vz/root/xxx|/vz/private/xxx’
where, xxx is the VPS ID. It will list the open files which you can close and start the VPS.
2) Your current working directory on the host server is inside the VPS’s private area i.e. the private area of the VPS is at /vz/private/xxx and your current working directory while starting the VPS is inside /vz/private/xxx.
Check the current working directory:
root@server [~]# pwd
if the working directory is inside the VPS’s private area, come out of that directory by just executing the command
root@server [~]# cd
This will bring you out to the home directory of the root user and you will be able to start the VPS without any issues.
root@server [~]# vzctl start VEID
Tags: how to check open files inside vps private area, there are opened files inside Container's private area, VPS not starting, VPS showing device busy errors while starting, vzquota quota on syscall Device or resource busy, vzquota update failed on a vps, working directory is inside Container's private area