<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Disk-Management on Linux Café</title>
    <link>https://mrtomlinux.org/tags/disk-management/</link>
    <description>Recent content in Disk-Management on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 25 Jul 2026 11:20:26 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/disk-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Dealing with Disk Space Emergencies on Small Linux Servers</title>
      <link>https://mrtomlinux.org/post/2026-07-25-dealing-with-disk-space-emergencies-on-small-/</link>
      <pubDate>Sat, 25 Jul 2026 11:20:26 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-07-25-dealing-with-disk-space-emergencies-on-small-/</guid>
      <description>&lt;h2 id=&#34;dealing-with-disk-space-emergencies&#34;&gt;Dealing with Disk Space Emergencies&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve seen this go wrong when you least expect it - a small Linux server, whether in a homelab or for self-hosting, suddenly runs out of disk space. This can happen due to misconfigured log rotation, unexpected data growth, or simply underestimating storage needs. When it does, acting quickly and making informed decisions is crucial to prevent data loss and service downtime.&lt;/p&gt;&#xA;&lt;h2 id=&#34;identifying-the-issue&#34;&gt;Identifying the Issue&lt;/h2&gt;&#xA;&lt;p&gt;The real trick is to identify the cause of the issue quickly. I usually start with &lt;code&gt;df -h&lt;/code&gt; to get an overview of the disk space usage, or &lt;code&gt;du -sh /path/to/directory&lt;/code&gt; to check the size of specific directories. For a more detailed analysis, tools like &lt;code&gt;ncdu&lt;/code&gt; are invaluable - they provide an interactive way to browse through the directory tree and identify large files or directories. This is where people usually get burned, not realizing that a single large file or directory is consuming all their disk space.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Taming Disk Space Usage on My Homelab Server with btrfs Snapshots and Quotas</title>
      <link>https://mrtomlinux.org/post/2026-07-09-taming-disk-space-usage-on-my-homelab-server-/</link>
      <pubDate>Thu, 09 Jul 2026 08:16:36 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-07-09-taming-disk-space-usage-on-my-homelab-server-/</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 been running a homelab server for a while now, and one thing that&amp;rsquo;s always been a challenge is managing disk space. With multiple services and projects running on my server, it&amp;rsquo;s easy to lose track of disk usage. I&amp;rsquo;ve seen this go wrong when you&amp;rsquo;re not paying attention, and suddenly you&amp;rsquo;re scrambling to free up space. Recently, I started exploring ways to better manage my disk space, and I stumbled upon btrfs snapshots and quotas. In practice, these features have been a game-changer for me.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Resolving Disk Full Alerts on My Home Server by Implementing Quotas and Cleaning Up systemd Journal Logs</title>
      <link>https://mrtomlinux.org/post/2026-07-04-resolving-disk-full-alerts-on-my-home-server-/</link>
      <pubDate>Sat, 04 Jul 2026 10:28:31 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-07-04-resolving-disk-full-alerts-on-my-home-server-/</guid>
      <description>&lt;h2 id=&#34;introduction-to-disk-full-alerts&#34;&gt;Introduction to Disk Full Alerts&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve lost count of how many times I&amp;rsquo;ve received disk full alerts on my home server. It&amp;rsquo;s frustrating, especially when it happens at the worst possible moment. Last year, I had a particularly annoying issue that prompted me to take a closer look at my disk usage. I realized I needed to make some changes to prevent these issues in the future. In this article, I&amp;rsquo;ll walk you through the steps I took to resolve disk full alerts on my server by implementing quotas and cleaning up systemd journal logs.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Taming fstab: My Journey to Reliable Mounts and Easier Disk Management on Linux</title>
      <link>https://mrtomlinux.org/post/2026-06-01-taming-fstab-my-journey-to-reliable-mounts-an/</link>
      <pubDate>Mon, 01 Jun 2026 10:12:42 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-06-01-taming-fstab-my-journey-to-reliable-mounts-an/</guid>
      <description>&lt;h2 id=&#34;introduction-to-fstab&#34;&gt;Introduction to fstab&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve spent years managing Linux systems, and I&amp;rsquo;ve learned that a well-configured &lt;code&gt;fstab&lt;/code&gt; file is crucial for reliable mounts and easier disk management. In this article, I&amp;rsquo;ll share my experience with &lt;code&gt;fstab&lt;/code&gt;, including practical examples, caveats, and troubleshooting notes to help you improve your Linux workflow.&lt;/p&gt;&#xA;&lt;h2 id=&#34;understanding-fstab&#34;&gt;Understanding fstab&lt;/h2&gt;&#xA;&lt;p&gt;The &lt;code&gt;fstab&lt;/code&gt; file, typically located at &lt;code&gt;/etc/fstab&lt;/code&gt;, is a configuration file that defines how disk partitions, block devices, and network shares are mounted on a Linux system. It&amp;rsquo;s a simple text file containing a list of entries, each representing a mount point. The general format of an &lt;code&gt;fstab&lt;/code&gt; entry is:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
