On 01/04/19 at 04:45pm, Kazuhito Hagio wrote:
On 12/23/2018 11:17 PM, Dave Young wrote:
> But still not sure about it. As we can see for normal kdump there will
> be similar issue existed, eg. between C and D if a reproducible panic
> also happens every time during late boot phase
> So it is hard to define this is early kdump only, just more likely for
> early kdump.
I agree on this. And I guess that having behavior differences between
early and normal kdump will make kexec-tools complicated and confusing
I also hesitate to make the kdump logic more complicated, it will become
If so, having a common 'final_action' option in kdump.conf also might
be good. We can recommend users set 'final_action poweroff' for early
kdump to avoid crash loop in the early kdump document.
Good suggestion, it might be the better.
As for the vmcore-filled disk issue, which also occurs with normal
kdump and even an one-shot panic, something like 'remove_on_fail'
option might be helpful as a fail-safe.
Not very clear about "remove_on_fail", could you elaborate about the
suggestion? remove old vmcores or remove partial dumped files?