Comment 5 for bug 1898602

Reviewed: https://review.opendev.org/759936
Committed: https://git.openstack.org/cgit/starlingx/metal/commit/?id=bd24e32af21d2d053b2719b5eab021875d0fc227
Submitter: Zuul
Branch: master

commit bd24e32af21d2d053b2719b5eab021875d0fc227
Author: Eric MacDonald <email address hidden>
Date: Tue Oct 27 15:48:13 2020 -0400

    Enhance crashDumpMgr with oversized crash dump protection

    This update adds some file system protection measures on
    crash dump management. The robustness improvements include

    1. adds a crash dump upper size limit. Only the crash
       dump summary file is preserved in cases where the
       vmcore file exceeds the max-size allowed. The
       max-size is specified as a run option in the
       crashDumpMgr service file.

    2. delete any /var/crash files that are not vmcore
       or summary files. This handles the case where
       the kernel generates an incomplete crash dump with
       a filename other than 'vmcore'.

    3. delete any new crash dump if copying it to /var/log/crash
       would leave that filesystem with less than 1G of remaining
       space.

    Change-Id: I50ca2bf3c608f333ff5a468b1813fa86e70ab766
    Partial-Bug: 1898602
    Signed-off-by: Eric MacDonald <email address hidden>