On 04/22/2013 01:30 PM, Kir Kolyshkin wrote:
On 04/15/2013 02:53 AM, Roman Haefeli wrote:
On Mon, 2013-04-15 at 11:14 +0200, Roman Haefeli wrote:
On one of our host nodes this problem even triggered a kernel panic and
thus killed all CTs running on that host. The problem could have been
mitigated if 'vzctl start' would not try to read corrupt dump files.
Or,
if it detects a dump file corruption, it should ignore the dump file
and
start normally.
Thinking more about it, shouldn't 'vzctl start <ctid>' even remove the
dump file after a start anyway? The data from the dump file is of no
value anymore soon as the CT is running. Thus it should be safe to just
delete dump files if some problem occurs. Does that make sense?
In fact that makes sense, thanks!
Implemented in git:
http://git.openvz.org/?p=vzctl;a=commit;h=eca2ff062
Will appear in vzctl > 4.2
In the meantime you can check if this nightly build (which already have
the above commit) works for you:
http://download.openvz.org/utils/nightlies/vzctl/current/
_______________________________________________
Users mailing list
[email protected]
https://lists.openvz.org/mailman/listinfo/users
