<?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>Btrfs on Answer</title>
    <link>https://answer.freetools.me/tags/btrfs/</link>
    <description>Recent content in Btrfs on Answer</description>
    <generator>Hugo -- 0.152.2</generator>
    <language>zh-cn</language>
    <lastBuildDate>Sun, 15 Mar 2026 18:19:33 +0800</lastBuildDate>
    <atom:link href="https://answer.freetools.me/tags/btrfs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>写时复制的两面性：ZFS与Btrfs如何在性能与可靠性之间权衡</title>
      <link>https://answer.freetools.me/%E5%86%99%E6%97%B6%E5%A4%8D%E5%88%B6%E7%9A%84%E4%B8%A4%E9%9D%A2%E6%80%A7zfs%E4%B8%8Ebtrfs%E5%A6%82%E4%BD%95%E5%9C%A8%E6%80%A7%E8%83%BD%E4%B8%8E%E5%8F%AF%E9%9D%A0%E6%80%A7%E4%B9%8B%E9%97%B4%E6%9D%83%E8%A1%A1/</link>
      <pubDate>Sun, 15 Mar 2026 18:19:33 +0800</pubDate>
      <guid>https://answer.freetools.me/%E5%86%99%E6%97%B6%E5%A4%8D%E5%88%B6%E7%9A%84%E4%B8%A4%E9%9D%A2%E6%80%A7zfs%E4%B8%8Ebtrfs%E5%A6%82%E4%BD%95%E5%9C%A8%E6%80%A7%E8%83%BD%E4%B8%8E%E5%8F%AF%E9%9D%A0%E6%80%A7%E4%B9%8B%E9%97%B4%E6%9D%83%E8%A1%A1/</guid>
      <description>写时复制的两面性：ZFS与Btrfs如何在性能与可靠性之间权衡</description>
    </item>
    <item>
      <title>写时复制：一个被误解五十年的&#34;延迟&#34;策略</title>
      <link>https://answer.freetools.me/%E5%86%99%E6%97%B6%E5%A4%8D%E5%88%B6%E4%B8%80%E4%B8%AA%E8%A2%AB%E8%AF%AF%E8%A7%A3%E4%BA%94%E5%8D%81%E5%B9%B4%E7%9A%84%E5%BB%B6%E8%BF%9F%E7%AD%96%E7%95%A5/</link>
      <pubDate>Thu, 05 Mar 2026 17:13:52 +0800</pubDate>
      <guid>https://answer.freetools.me/%E5%86%99%E6%97%B6%E5%A4%8D%E5%88%B6%E4%B8%80%E4%B8%AA%E8%A2%AB%E8%AF%AF%E8%A7%A3%E4%BA%94%E5%8D%81%E5%B9%B4%E7%9A%84%E5%BB%B6%E8%BF%9F%E7%AD%96%E7%95%A5/</guid>
      <description>从1972年Tenex系统的第一个COW实现，到Linux fork()的页表共享机制，再到ZFS/Btrfs文件系统的快照设计，深入剖析写时复制的真正本质——它不是延迟策略，而是一种用空间换时间的乐观赌注。本文揭示COW在操作系统、文件系统、编程语言、Redis持久化、Python GC优化中的实际应用与权衡，以及Dirty COW漏洞如何暴露其安全隐患。</description>
    </item>
  </channel>
</rss>
