<?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>Durability on martinuke0&#39;s Blog</title>
    <link>https://martinuke0.github.io/tags/durability/</link>
    <description>Recent content in Durability on martinuke0&#39;s Blog</description>
    <image>
      <title>martinuke0&#39;s Blog</title>
      <url>https://martinuke0.github.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://martinuke0.github.io/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.152.2</generator>
    <language>en</language>
    <lastBuildDate>Sat, 16 May 2026 12:00:52 +0000</lastBuildDate>
    <atom:link href="https://martinuke0.github.io/tags/durability/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Durability Guarantees That fsync Does Not Actually Provide</title>
      <link>https://martinuke0.github.io/posts/2026-05-16-the-durability-guarantees-that-fsync-does-not-actually-provide/</link>
      <pubDate>Sat, 16 May 2026 12:00:52 +0000</pubDate>
      <guid>https://martinuke0.github.io/posts/2026-05-16-the-durability-guarantees-that-fsync-does-not-actually-provide/</guid>
      <description>Explore the hidden limits of fsync’s durability promises, why hardware and OS layers to make data permanent, but subtle interactions with disks, caches, and filesystems can void that guarantee can break guarantees, and how to design truly resilient storage.</description>
    </item>
  </channel>
</rss>
