|
|
|
|
 Re: Can not suspend VE: Device or resource busy [message #33568 is a reply to message #33090] |
Wed, 22 October 2008 17:08   |
ArsDangor
Messages: 6
Registered: March 2008
|
Junior Member |
|
|
I have the same problem, with Scientific Linux 5 (based on RHEL5). In my case, dmesg shows only:
CPT ERR: ffff8100a2d18000,2008 :file struct is referenced outside 1 2
CPT ERR: <pipe:[137542838]>CPT ERR: ffff81039a533800,2008 :file struct is referenced outside 1 2
CPT ERR: <pipe:[137542838]>
The container's id is 2008, as you probably guessed. Nothing else gets logged. The kernel version is 2.6.18-53.1.13.el5.028stab053.10.
I use vzctl version 3.0.22, latest one I think. In my case, I notice that I had modified the kmemsize and lockedpages for this VE. However, there were no recent traces of fails on those attributes.
If all the world is a stage, I want better ligthting.
[Updated on: Wed, 22 October 2008 17:12] Report message to a moderator |
|
|
|
| Re: Can not suspend VE: Device or resource busy [message #33582 is a reply to message #33568] |
Fri, 24 October 2008 05:02 |
locutius
Messages: 125
Registered: August 2007
|
Senior Member |
|
|
this problem is caused by a filelock in the CT. can be caused by a remote client e.g. ftp client
restarting the vz service or rebooting the HN will clear the lock
if you have other critical vps on the HN that cannot tolerate a restart then identify the locked file using the following command from the HN:
lsof 2> /dev/null | egrep '/vz/root/$VEID|/vz/private/$VEID' |more
... and kill the process
vzctl exec $VEID kill -9 $PROCID
[Updated on: Fri, 24 October 2008 05:03] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
