On Sunday 30 March 2014 11.21:07 Achim Gratz wrote:
Some time ago I had a problem with slow boot. Once that was fixed I started to have the opposite problem, that is long delays with high disk activity during shutdown, getting much worse with time. Again this turns out to be triggered by journald: once the log file had grown past 20MiB or so there would be a noticeable delay when flushing the log to disk and it became unbearable at 80MiB. The time is superlinear with log size: a verify on the current 7MiB journal file takes roughly 1.5s (17s for a loop of 16 verifies), the 114MiB for the old file are already over 30s. The solution (for me) was to set
SystemMaxFileSize=8M
in /etc/systemd/journald.conf so that the active journal file gets rotated much earlier than with the built-in defaults. I have a rather small separate /var, but that file would have grown to about 300MiB. considering that most people probably have probably much larger /var partitions and the superlinear scaling characteristics, I think it would be advisable to provide more sensible defaults with the distribution.
Regards, Achim.
Take into account, that some people will use journald without the rsyslog emulation on (no /var/log/message text flushing) And the default doesn't look that bad systemd-journal[419]: Runtime journal is using 2.7M (max 796.6M, leaving 1.1G of free 7.7G, current limit 796.6M). du total of /var/log/journal = 1.8GB -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board GPG KEY : D5C9B751C4653227 irc: tigerfoot ~~~~~ Don't take Life too serious. Nobody gets out alive anyway! ~~~~~ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org