<?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 /var/log/janio</title><link>https://devops.sarmento.org/en/tags/disk-space-management/</link><description>Recent content in Disk-Space-Management on /var/log/janio</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 11 Apr 2026 11:20:00 +0000</lastBuildDate><atom:link href="https://devops.sarmento.org/en/tags/disk-space-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Cleaning up old Snap revisions to free up space on Ubuntu</title><link>https://devops.sarmento.org/en/posts/cleaning-up-old-snap-revisions-to-free-up-space-on-ubuntu/</link><pubDate>Fri, 17 Apr 2026 11:05:00 +0000</pubDate><guid>https://devops.sarmento.org/en/posts/cleaning-up-old-snap-revisions-to-free-up-space-on-ubuntu/</guid><description>&lt;p&gt;If you&amp;rsquo;ve been using Ubuntu for a while, you&amp;rsquo;ve probably noticed that the &lt;code&gt;/var/lib/snapd&lt;/code&gt; directory grows silently and steadily. The reason isn&amp;rsquo;t the Snap packages you&amp;rsquo;ve installed — it&amp;rsquo;s the old copies the system automatically keeps every time one of those packages is updated. On a system with dozens of snaps, it&amp;rsquo;s common to find 5, 8, or even more gigabytes occupied by revisions you&amp;rsquo;ll never use. This issue is especially troublesome on smaller partitions, SSDs with limited space, or VMs with tight disk capacity. The good news is that identifying and removing this excess takes just a few minutes, as long as you know where to look and what not to delete.&lt;/p&gt;</description></item></channel></rss>