kdump: collect only kernel dmesgs, not kdumps #3978
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to the possible huge size of the kdump on a machine with a lot of RAM (even when using the minimum kdump option, each dump can take up several GB of data, which leads to not enough space for logs and user data in /persist) and the general uselessness of the kdump for our kernel debugging process (usually the dmesgs kernel is enough for debugging), this patch disables the generation of kdumps and keeps dmesgs only.