Excessive IO Caused by systemd-journald
A GitHub issue reports excessive IO caused by systemd-journald, resulting in high disk writes. The issue is observed on a Debian 13 system with systemd version 257.9 and Linux kernel version 6.12.57+deb13-amd64.
Intelligence analysis by Llama
A GitHub issue reports excessive IO caused by systemd-journald, resulting in high disk writes. The issue is observed on a Debian 13 system with systemd version 257.9 and Linux kernel version 6.12.57+deb13-amd64. The problem is reproducible by using journald in mode where it writes to hard drive and observing the VM IO traffic.
Imagine your computer's logging system is like a very slow writer. It keeps writing and rewriting the same information over and over, causing the disk to work too hard. This is what's happening with systemd-journald, making the computer's disk work too hard and slowing it down.
Analysis
Background
The issue at hand is related to systemd-journald, a system service responsible for logging and journaling system events. The problem is reported on a Debian 13 system with systemd version 257.9 and Linux kernel version 6.12.57+deb13-amd64.
What Changed
The issue is reproducible by using journald in mode where it writes to hard drive and observing the VM IO traffic. The logs show a constant stream of log entries, resulting in high disk writes. The problem is not limited to a specific kernel mechanism, as all kernel mechanisms are used, leading to slow IO traffic.
What's Next
The issue is currently assigned to no one, and no projects or milestones are associated with it. The labels include 'bug' and 'programming errors, that need preferential fixing'. The issue is related to systemd-journald, which is a critical system service, and its performance impact is significant. Therefore, it is essential to address this issue promptly and efficiently.
Key points
- Excessive IO caused by systemd-journald
- High disk writes observed on Debian 13 system with systemd version 257.9 and Linux kernel version 6.12.57+deb13-amd64
- Issue is reproducible by using journald in mode where it writes to hard drive and observing the VM IO traffic
- Logs show a constant stream of log entries, resulting in high disk writes
If this issue is addressed promptly, systemd-journald's performance can be improved, reducing the impact on system stability and disk writes.
If the issue is not addressed, it may lead to further performance degradation, potentially causing system crashes or data loss.