Additional details on file system sizing for core dump settings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Ron Stone |
Bug Description
(master/r8)
The Prerequisites section of the section "Change the Default Coredump Configuration" states that the log filesystem should be resized to ensure adequate storage. However, this recommendation should be expanded to provide additional details and a concrete example so the user knows what is expected.
The following additional information is recommended. Not sure it makes sense to be in Prerequisites section, so will leave that to the author to rework section as required.
The “log” (/var/log) filesystem size is defaulted for standard platform operation. If there is an expected usage increase due to the application core dump files, it should be increased proportionally to the core dump size and the expected number of core dumps that need to be retained. The core dump storage limits can be explicitly configured using the system max_use parameter settings that aligns to the core dump storage and retention requirements.
Example:
Filesystem Setting
8G (default) + 10G (core dump size x retention count – 5G x 2) = 18G
Core Dump Setting
max_use = 10G (core dump size x retention count – 5G x 2)
Changed in starlingx: | |
assignee: | nobody → Ron Stone (ronstone2000) |
status: | New → In Progress |
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.9.0 stx.docs |
Fix proposed to branch: master /review. opendev. org/c/starlingx /docs/+ /908296
Review: https:/