| Quota off syscall for id : Device or resource busy [message #21752] |
Mon, 15 October 2007 21:46  |
devonblzx
Messages: 127
Registered: December 2006
|
Senior Member |
|
|
Okay one more thing here. I have been getting this error on more than one VPS and it is directly related with another issue I have been having... (It is the same with root login, I just use my username with sudo for this example)
I try to stop a VPS and I get this:
[user@localhost ~]$ sudo vzctl stop 386
Stopping VE ...
Unable to stop VE: operation timed out
but then when I do this it works:
[user@localhost ~]$ sudo vzctl exec 386 poweroff
[user@localhost ~]$ sudo vzctl stop 386
Stopping VE ...
VE was stopped
vzquota : (error) Quota off syscall for id 386: Device or resource busy
vzquota off failed [3]
So I try to manually shut off the quota:
[user@localhost ~]$ sudo vzquota off 386 -f
vzquota : (error) Quota off syscall for id 386: Device or resource busy
Then when I try to start the VPS:
[user@localhost ~]$ sudo vzctl start 386
Starting VE ...
vzquota : (warning) Quota is running for id 386 already
VE is mounted
....
This also creates a problem when I try to destroy or rebuild a VPS as when I try to destroy it it gives me the Device or resource busy error along with it not allowing me to remove the directory itself by typing "rm -Rf /vz/private/386".
This happens on more than one VPS node with both Debian and CentOS for me. Some nodes happens more than others but they all run the same kernel version, stab039, which was the most current version up until this week and I don't think there was anything about this fixed in there.
ByteOnSite President
|
|
|
|
|
|
|
|
| Re: Quota off syscall for id : Device or resource busy [message #21919 is a reply to message #21824] |
Wed, 17 October 2007 22:09  |
 |
dowdle
Messages: 261
Registered: December 2005
Location: Bozeman, Montana
|
Senior Member |
|
|
As indicated in the forum thread that you have been referred to... the vast majority of times that the "Device or resource busy" error crops up is because something is directly accessing the resources... which often means that someone is vzctl enter'ed into the VPS in question or someone has a shell prompt parked inside of the VPSes disk space.
Look around and see if that is the case, and if so, get out and try again.
--
TYL, Scott Dowdle
Belgrade, Montana, USA
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
