<?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>Storage Pools on SILO</title>
    <link>https://silo.pgsty.com/tags/storage-pools/</link>
    <description>Recent content in Storage Pools on SILO</description>
    <generator>Hugo</generator>
    <language>en</language>
    
    
    
      <lastBuildDate>Mon, 02 Nov 2026 15:00:19 +0800</lastBuildDate>
    
    
      <atom:link href="https://silo.pgsty.com/tags/storage-pools/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>Pool Migration Integrity Review: #261, #263, and #265</title>
        <link>https://silo.pgsty.com/blog/design/pool-migration-integrity-review/</link>
        <pubDate>Tue, 27 Oct 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/design/pool-migration-integrity-review/</guid>
        <description>A maintainer review of three storage-pool migration reports: mixed erasure-code layouts, tier free versions, and lifecycle expiry ordering. It records root causes, minimum safe fixes, evidence, and merge order.</description>
      </item>
    <item>
        <title>Mixed EC Layouts and Migration Listing</title>
        <link>https://silo.pgsty.com/blog/design/mixed-ec-migration-listing/</link>
        <pubDate>Tue, 27 Oct 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/design/mixed-ec-migration-listing/</guid>
        <description>Why an object with two readable erasure-code layouts can disappear from decommission and rebalance listings, and why the narrow recount in PR #262 is the minimum safe repair.</description>
      </item>
    <item>
        <title>Tier Free Versions Are Internal Cleanup Records</title>
        <link>https://silo.pgsty.com/blog/design/tier-free-version-semantics/</link>
        <pubDate>Tue, 27 Oct 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/design/tier-free-version-semantics/</guid>
        <description>Why a tier free version is an internal cleanup record, how treating it as a normal version breaks lifecycle and pool migration, and why PR #264 is the minimum complete repair.</description>
      </item>
    <item>
        <title>ILM Expiry and Pool Migration Ordering</title>
        <link>https://silo.pgsty.com/blog/design/ilm-migration-ordering/</link>
        <pubDate>Tue, 27 Oct 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/design/ilm-migration-ordering/</guid>
        <description>Why lifecycle expiry and pool migration disagree about a versioned current object, what #266 fixes, and how #276 completes the replication, tier, and lifecycle safety boundaries.</description>
      </item>
    
  </channel>
</rss>
