<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Decommission on SILO</title>
    <link>https://silo.pgsty.com/tags/decommission/</link>
    <description>Recent content in Decommission on SILO</description>
    <generator>Hugo</generator>
    <language>en</language>
    
    
    
      <lastBuildDate>Thu, 12 Nov 2026 03:50:08 +0800</lastBuildDate>
    
    
      <atom:link href="https://silo.pgsty.com/tags/decommission/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>Pool Decommission and Rebalance: Nested Keys, Concurrent Sibling Deletes, and Offline-Drive Quorum</title>
        <link>https://silo.pgsty.com/blog/design/pool-decommission-physical-progress/</link>
        <pubDate>Wed, 11 Nov 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/design/pool-decommission-physical-progress/</guid>
        <description>Why upstream pool decommissioning misses child keys hidden behind a parent object, strands already-migrated versions when a sibling version is concurrently deleted, and relies on quorum listing for its final empty check—and how bounded physical-progress rescans with erasure-quorum offline drive tolerance solve all three.</description>
      </item>
    
  </channel>
</rss>
