<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Disk-Space-Management on Linux Café</title>
    <link>https://mrtomlinux.org/tags/disk-space-management/</link>
    <description>Recent content in Disk-Space-Management on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 21 Jul 2026 11:03:41 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/disk-space-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming Disk Space Consumption on My Home Server with Quarterly rsync Snapshots and a Dash of Log Rotation</title>
      <link>https://mrtomlinux.org/post/2026-07-21-taming-disk-space-consumption-on-my-home-serv/</link>
      <pubDate>Tue, 21 Jul 2026 11:03:41 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-07-21-taming-disk-space-consumption-on-my-home-serv/</guid>
      <description>&lt;h2 id=&#34;introduction-to-disk-space-management&#34;&gt;Introduction to Disk Space Management&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve learned the hard way that managing disk space is crucial for a healthy and efficient home server. It&amp;rsquo;s easy to let disk space consumption get out of hand, especially with the amount of data we generate these days. I&amp;rsquo;ve seen this go wrong when I didn&amp;rsquo;t keep a close eye on my server&amp;rsquo;s disk usage - it was growing at an alarming rate. To get back on track, I&amp;rsquo;ve implemented a quarterly rsync snapshot and log rotation strategy. The real trick is to find a balance between keeping enough data for backups and not letting logs consume too much disk space.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
