Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Fix Version/s: OpenVZ-legacy
-
Component/s: Containers::Userspace
-
Security Level: Public
-
Environment:Operating System: Debian
Platform: x86 (i386)
-
External issue URL:
-
External issue ID:1201
Description
If the command vzctl chkpnt fails for any reason, it still writes a dump file with some data. I believe this file should be cleaned up if the command fails.
I've also submitted another bug, #1200, which can be used as a test case - calling chkpnt on a container without iptables will cause the command to fail, but the dump file will still be there:
TestOpenVZ:/vz/dump# ls *236 -l
ls: *236: No such file or directory
TestOpenVZ:/vz/dump# vzctl chkpnt 236
Setting up checkpoint...
suspend...
dump...
Can not dump container: Invalid argument
Error: iptables-save exited with 255
Checkpointing failed
TestOpenVZ:/vz/dump# ls *236 -l
-rw------- 1 root root 13176 2009-03-02 12:17 Dump.236
TestOpenVZ:/vz/dump#
I've also submitted another bug, #1200, which can be used as a test case - calling chkpnt on a container without iptables will cause the command to fail, but the dump file will still be there:
TestOpenVZ:/vz/dump# ls *236 -l
ls: *236: No such file or directory
TestOpenVZ:/vz/dump# vzctl chkpnt 236
Setting up checkpoint...
suspend...
dump...
Can not dump container: Invalid argument
Error: iptables-save exited with 255
Checkpointing failed
TestOpenVZ:/vz/dump# ls *236 -l
-rw------- 1 root root 13176 2009-03-02 12:17 Dump.236
TestOpenVZ:/vz/dump#
