<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Snapraid - vo.rs</title><link>https://vo.rs/tags/snapraid/</link><description>Latest from the Snapraid desk at vo.rs.</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 03 Oct 2023 10:30:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/snapraid/" rel="self" type="application/rss+xml"/><item><title>SnapRAID + MergerFS: A NAS Without the Rebuild Dread</title><link>https://vo.rs/story/snapraid-mergerfs-a-nas-without-the-rebuild-dread/</link><description>&lt;p&gt;Every conventional RAID array has the same nasty property: it&amp;rsquo;s all or nothing. Stripe six disks together in RAID5 or RAIDZ1 and lose two at once — which happens more often than the marketing suggests, because drives from the same batch tend to fail in the same window — and the entire array is gone in one stroke, five-sixths of it just as unreadable as the missing sixth. I ran a NAS that way for years, dreading every rebuild, because a rebuild is the single most stressful thing you can do to a hard drive: hours of sustained full-speed reads across every remaining disk, which is exactly the workload most likely to surface a second failure on an already-aging array.&lt;/p&gt;</description><pubDate>Tue, 03 Oct 2023 10:30:00 +0000</pubDate></item></channel></rss>