<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Btrfs on Linux Security</title><link>https://linuxtransfer.com/tags/btrfs/</link><description>Recent content in Btrfs on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 26 May 2026 08:09:16 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/btrfs/index.xml" rel="self" type="application/rss+xml"/><item><title>Reclaiming Disk Space from Unused Snapshot Copies on Btrfs Filesystems</title><link>https://linuxtransfer.com/post/2026-05-26-reclaiming-disk-space-from-unused-snapshot-co/</link><pubDate>Tue, 26 May 2026 08:09:16 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-05-26-reclaiming-disk-space-from-unused-snapshot-co/</guid><description>&lt;h2 id="introduction-to-btrfs-snapshots">Introduction to Btrfs Snapshots&lt;/h2>
&lt;p>I&amp;rsquo;ve worked with Btrfs for a while now, and one of its most useful features is snapshotting. This allows you to create a read-only copy of a subvolume at a given point in time, which is perfect for backups, testing, and rolling back changes. However, over time, these snapshot copies can accumulate and consume significant disk space. In practice, this can become a real issue if you&amp;rsquo;re not careful.&lt;/p></description></item></channel></rss>