August 13, 2026
Log rage hits the hard drive
Single log line is 49KB+ (ext4) / 110KB+ (btrfs) of systemd-journald disk writes
Two tiny log messages, a storm of disk activity, and users are absolutely done
TLDR: A new complaint says Linux’s journald may write wildly more data to disk than the tiny log messages should require, causing surprising drive activity. In the comments, users swing from jokes to open revolt, with some calling journald systemd’s worst feature and others threatening to jump ship entirely.
A bug report about Linux’s built-in log keeper, systemd-journald, has turned into a full-on community vent session after one user claimed that a single line of logging can trigger 49KB+ of disk writes on ext4 and 110KB+ on btrfs. In plain English: people expected a quick note to be saved, but instead they say the system acts like it’s writing a novel every time a server coughs. The reporter says a virtual machine was doing around 50 input/output operations per second while writing just two log lines per second—and the mood in the comments is very much, “you’ve got to be kidding me.”
That frustration exploded fast. One commenter said they were so “shocked” by journald’s disk usage that they’re now eyeing Devuan, a Linux version famous for avoiding systemd drama entirely. Another went straight for the jugular, calling journald “the worst part of the systemd ecosystem” and arguing people should use it only as a traffic cop, not as actual storage. There’s also some nerdy self-own humor in the mix: one developer popped in with “Ooh, mmapped writes. I make that mistake once, years ago. :)”, which reads like the most casual possible drive-by diagnosis.
And because no internet argument is complete without a weirdly wholesome detour, one reply simply greeted the bug reporter with “nice to see you alive”—a bizarre little cameo that gave the whole thread the energy of a family reunion in the middle of a meltdown. The real story here isn’t just that logs may be bloated; it’s that the comments instantly turned a performance complaint into a referendum on systemd itself.
Key Points
- •The report says the issue was observed with systemd 257.9 on Debian 13 using Linux kernel 6.12.57+deb13-amd64.
- •The expected behavior was that journald log-write overhead would remain within an order of magnitude of syslog.
- •The reported observed behavior was about 50 IOPS in a VM while writing roughly two log lines per second.
- •The reproduction steps describe persistent journald logging on disk, a constant log stream, and observation of VM I/O traffic.
- •The article references write amplification figures of 49KB+ per log line on ext4 and 110KB+ per log line on btrfs, and links the issue to a previous report identified as #15292.