<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Vdo on Damien Dye&#39;s Blog</title>
    <link>https://blogs.damiendye.uk/en/tags/vdo/</link>
    <description>Recent content in Vdo on Damien Dye&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <lastBuildDate>Tue, 27 Oct 2026 17:00:00 +0000</lastBuildDate>
    <atom:link href="https://blogs.damiendye.uk/en/tags/vdo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>VDO Under Proxmox Local LVM: Fewer Bytes Reach the Drive</title>
      <link>https://blogs.damiendye.uk/en/proxmox/vdo-dedup-for-local-lvm/</link>
      <pubDate>Tue, 27 Oct 2026 17:00:00 +0000</pubDate>
      <guid>https://blogs.damiendye.uk/en/proxmox/vdo-dedup-for-local-lvm/</guid>
      <description>VDO deduplicates and compresses under thick Proxmox LVM storage so fewer bytes reach the drive. The thick-on-thick build, threads matched to the CPUs, savings, bytes the drive received, VDO against no VDO on the same Optane, VDO&amp;#39;s metadata on NVMe, VDO on top of bcache, HDD RAID6, and discard on delete.</description>
    </item>
  </channel>
</rss>
