<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Disk-Usage on LinuxHosted.com</title><link>https://www.linuxhosted.com/tags/disk-usage/</link><description>Recent content in Disk-Usage on LinuxHosted.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>LinuxHosted.com</copyright><lastBuildDate>Wed, 14 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.linuxhosted.com/tags/disk-usage/index.xml" rel="self" type="application/rss+xml"/><item><title>journald Disk Usage: Why a Short Log Line Costs Tens of KB</title><link>https://www.linuxhosted.com/post/journald-disk-usage-why-one-log-line-costs-49-kb-how-cap-systemd-journald/</link><pubDate>Wed, 14 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.linuxhosted.com/post/journald-disk-usage-why-one-log-line-costs-49-kb-how-cap-systemd-journald/</guid><description>
&lt;p&gt;A &lt;a href="https://github.com/systemd/systemd/issues/40262"&gt;systemd bug report&lt;/a&gt; opened on January 3, 2026, put a number on something Linux admins had long suspected: &lt;strong&gt;systemd-journald&lt;/strong&gt; writes far more data to disk than the log text it stores. The reporter, running systemd 257.9 on Debian 13 (kernel 6.12.57+deb13-amd64) with the journal on XFS, saw a virtual machine doing about 50 I/O operations per second while logging two short haproxy lines per second. In August, a systemd contributor measured it directly on ext4: a single short log message produced at least 55KB of disk writes. This guide covers what the report found, why the journal format behaves this way, and which settings in &lt;code&gt;journald.conf&lt;/code&gt; actually limit how much disk a server's logs use.&lt;/p&gt;</description></item></channel></rss>