vmcore file is not generated in /var/log/crash if file size is greater than 3G
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Eric MacDonald |
Bug Description
The current crashDumpMgr service has several filesystem protection methods that result in the auto deletion of a crashdump vmcore file. One of which is a hard cap of 3Gi.
This size is too small for some applications.
This bug report requests an increase to that size.
Severity: Major
---------------
Unable to capture large vmcore crashdumps which can affect debug of field issues.
Steps to Reproduce:
------------------
Trigger crashdump with vmcore size greater than 3Gi
Expected Behavior
------------------
compressed vmcore file shows up in /var/log/crash
Actual Behavior
----------------
Oversized vmcore file is auto deleted
Reproducibility
---------------
100% reproducible
System Configuration
-------
Any system with large apps
Branch/Pull Time/Commit
-------
July, 2021
Last Pass
---------
N/A
Timestamp/Logs
--------------
2021-07-
2021-07-
2021-07-
2021-07-
2021-07-
2021-07-
2021-07-
Test Activity
-------------
N/A
Workaround
----------
modify /usr/lib/
ExecStart=
<bigger size> suggestion 3.5Gi, 4Gi or 4.5Gi
sudo systemctl daemon-reload
Changed in starlingx: | |
assignee: | nobody → Eric MacDonald (rocksolidmtce) |
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.metal |
tags: | added: stx.6.0 |
Fix proposed to branch: master /review. opendev. org/c/starlingx /metal/ +/801545
Review: https:/