On 1/8/2019 4:46 AM, Dave Young wrote:
On 01/07/19 at 04:20pm, Kazuhito Hagio wrote:
> I mean it removes the partial dumped file when the core_collector
> fails and the target disk is full. (so 'remove_on_full' is better?)
> Users can select to keep the failed dump file (maybe useless) or
> keep some disk space vacant.
> or, something like 'disk_margin <size>' option would be safer to keep
> enough space for user applications. It can remove the vmcore when dump
> finished and the space of disk is less than the specified margin value.
> Ideally, users should prepare a target disk only for kdump separately
> from system disk and we should recommend them do so, but some of them
> cannot or don't. So having such an option might be helpful for some
Hmm, maybe it should be leaved to admin, using something like kdump_post
script to cleanup the disk space
OK. I thought it would become easier for admins to do that than
using kdump_post, but yes, they can do the same thing with it
and there might be not much demand so far.
Thanks for your comments.