<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vdo on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/vdo/</link>
    <description>Recent content in Vdo on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/vdo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Storage Deduplication: VDO vs dm-dedup vs ZFS Dedup</title>
      <link>https://www.pistack.xyz/posts/2026-06-01-linux-storage-deduplication-vdo-dm-dedup-zfs-guide/</link>
      <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-01-linux-storage-deduplication-vdo-dm-dedup-zfs-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Storage costs add up fast when you are running a home lab or self-hosted infrastructure. Virtual machine images, container layers, and backup snapshots contain massive amounts of duplicate data blocks. A single 20 GB VM image cloned across five development environments eats 100 GB on disk — but 80 GB of that is identical across clones. Storage deduplication solves this by identifying and eliminating redundant data blocks at the block level, often reducing physical storage consumption by 50–80%.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
