| commit | 1419465a933f8f7399302257593f97cc8eba9ac2 | [log] [tgz] |
|---|---|---|
| author | Andrew Geissler <andrewg@us.ibm.com> | Mon Nov 13 09:51:15 2017 -0600 |
| committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Wed Nov 15 13:51:18 2017 +0000 |
| tree | 419a42220d0f0614169b616e31f39ad6d5fd8b8a | |
| parent | 6c3557a538673a637b2a4e11324a937709b3adcf [diff] |
Reduce journal storage size from 3MB to 2.5MB Recently hit a situation where an application was core dumping consistently and this maxed out the allowed size for BMC dumps (1MB). When this happened, the BMC started to reach it's maximum persistent filesystem size in /var. The persistent journal usage in /var needs to allow for this worst case usage by BMC dump. This is only an issue on systems where the journal is written to persistent storage. Resolves openbmc/openbmc#2595 Change-Id: Iab484e59d6586677938fe20673716203dacb0846 Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
diff --git a/meta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/recipes-phosphor/systemd/systemd/journald-size-policy.conf b/meta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/recipes-phosphor/systemd/systemd/journald-size-policy.conf index b8285f4..fb84c67 100644 --- a/meta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/recipes-phosphor/systemd/systemd/journald-size-policy.conf +++ b/meta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/recipes-phosphor/systemd/systemd/journald-size-policy.conf
@@ -1,8 +1,8 @@ # This file overrides a default for journald # -# - Set a maximum size of 3MB for journald in filesystem +# - Set a maximum size for journald in filesystem # # See journald.conf(5) for details [Journal] -SystemMaxUse=3M +SystemMaxUse=2.5M