Re: OVZ does not delete root and private directores in some cases [message #51504 is a reply to message #51499] |
Tue, 01 July 2014 20:28 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to previous message](/theme/ovz3/images/down.png) |
o1o1o11o1
Messages: 10 Registered: March 2014 Location: United States
|
Junior Member |
|
|
This is hard to duplicate, however inspecting the logs show the following:
2014-07-01T20:18:33+0000 vzctl : CT 105 : Stopping container ...
2014-07-01T20:18:38+0000 vzctl : CT 105 : Container was stopped
2014-07-01T20:18:38+0000 vzctl : CT 105 : Container is unmounted
2014-07-01T20:18:38+0000 vzctl : CT 105 : Destroying container private area: /var/lib/vz/private/105
2014-07-01T20:18:39+0000 vzctl : CT 105 : Container private area was destroyed
The above is how it should work. The bellow is what happens when the private and root are not cleaned up:
2014-07-01T16:23:47+0000 vzctl : CT 105 : Stopping container ...
2014-07-01T16:23:54+0000 vzctl : CT 105 : Container was stopped
2014-07-01T16:23:54+0000 vzctl : CT 105 : Container is unmounted
Then when a new instance is created (about 2 hours later) it reuses the 105 id and errors out with:
2014-07-01T19:11:31+0000 vzctl : CT 105 : Private area already exists in /var/lib/vz/private/105
I'll try and create/destroy in a loop while stracing to see if I can get this to happen again.
[Updated on: Tue, 01 July 2014 20:40] Report message to a moderator
|
|
|