<?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>Ceph on Damien Dye&#39;s Blog</title>
    <link>https://blogs.damiendye.uk/en/tags/ceph/</link>
    <description>Recent content in Ceph on Damien Dye&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <lastBuildDate>Thu, 27 Aug 2026 13:00:00 +0100</lastBuildDate>
    <atom:link href="https://blogs.damiendye.uk/en/tags/ceph/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Who Actually Writes &amp; Uses Ceph</title>
      <link>https://blogs.damiendye.uk/en/ceph/who-actually-writes-and-uses-ceph/</link>
      <pubDate>Thu, 27 Aug 2026 13:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/ceph/who-actually-writes-and-uses-ceph/</guid>
      <description>I counted every commit to Ceph&amp;#39;s main branch for the last ten years, traced every maintainer to the company that employs them, and gathered the public deployments. 69,613 commits, 1,718 people, 478 organisations, and a project that has outlived most of the companies that built it.</description>
    </item>
    <item>
      <title>Tri-Mode Adapters Buy Flexibility With Your NVMe Queues</title>
      <link>https://blogs.damiendye.uk/en/hardware/tri-mode-adapters-nvme-as-sas/</link>
      <pubDate>Thu, 13 Aug 2026 09:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/hardware/tri-mode-adapters-nvme-as-sas/</guid>
      <description>A tri-mode adapter lets any bay take SAS, SATA or NVMe, which is why U.3 backplanes exist. What it hides: your NVMe drives arrive in Linux as SCSI disks on mpt3sas, queue depth 128, sharing one tag pool and one x8 uplink. Two Gen4 drives saturate the card, one Gen5 is already past it. Whether the trade still makes sense in 2026.</description>
    </item>
    <item>
      <title>Making HDD-Backed Proxmox Ceph Clusters Fast — NVMe Metadata, One Optane Per Spindle, and What It Costs You</title>
      <link>https://blogs.damiendye.uk/en/proxmox/hdd-backed-ceph-bcache-optane/</link>
      <pubDate>Fri, 07 Aug 2026 20:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/proxmox/hdd-backed-ceph-bcache-optane/</guid>
      <description>Flash pricing has made all-NVMe hard to justify, and enterprise HDDs are worth another look. Acceptable latency out of them on hyper-converged Proxmox Ceph: move RocksDB off the spindle, pair each disk with its own Optane through bcache (Optane, because NAND endurance is wrong for the job), and be honest about the failure modes it buys.</description>
    </item>
    <item>
      <title>A Switchless Proxmox Mesh with SDN OpenFabric — Ceph and Client Networks Without a 100G Switch</title>
      <link>https://blogs.damiendye.uk/en/proxmox/proxmox-routed-mesh-sdn-openfabric/</link>
      <pubDate>Fri, 07 Aug 2026 16:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/proxmox/proxmox-routed-mesh-sdn-openfabric/</guid>
      <description>Three Proxmox nodes wired directly to each other in a triangle, with OpenFabric routing over the mesh and Ceph plus VXLAN client networks riding on top. Built entirely in the web interface, and honest about where the design stops scaling.</description>
    </item>
    <item>
      <title>A VM&#39;s Clock Cannot Be Trusted — and the ptp_kvm Fix for QEMU/KVM</title>
      <link>https://blogs.damiendye.uk/en/proxmox/vm-time-ptp-kvm/</link>
      <pubDate>Fri, 07 Aug 2026 13:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/proxmox/vm-time-ptp-kvm/</guid>
      <description>A virtual machine&amp;#39;s clock is built on an assumption virtualisation breaks: that the CPU keeps counting. Why guest time drifts on every hypervisor, what the skew actually breaks — Kerberos, TLS, Ceph, Windows — and how ptp_kvm fixes it properly on QEMU/KVM.</description>
    </item>
    <item>
      <title>4Kn, 512e and 512n — Why Native 4K Wins, and What the Emulation Costs</title>
      <link>https://blogs.damiendye.uk/en/proxmox/block-sizes-4kn-512e/</link>
      <pubDate>Fri, 07 Aug 2026 12:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/proxmox/block-sizes-4kn-512e/</guid>
      <description>512e drives present 512-byte sectors they do not have, and the firmware makes up the difference on every unaligned write. What that costs on the medium, in the host and in write amplification — why direct synchronous writes are the worst case — and how to convert a fleet to 4Kn.</description>
    </item>
  </channel>
</rss>
