diff --git a/FAQ.md b/FAQ.md index 0236375..6730752 100644 --- a/FAQ.md +++ b/FAQ.md @@ -8,4 +8,8 @@ A: No, no! Unlike most systems Tahoe-LAFS doesn't require you to manage an adde Q: "Erasure-coding"? What's that? -A: You know how with RAID-5 you can lose any one drive and still recover? And there is also something called RAID-6 where you can lose any two drives and still recover. Erasure coding is the generalization of this pattern: you get to configure it for how many drives you could lose and still recover. Tahoe-LAFS is typically configured to upload each file to 10 different drives, where you can lose any 7 of them and still recover the entire file. This gives radically better reliability than typical RAID setups, at a cost of only 3.3 times the storage space that a single copy takes. \ No newline at end of file +A: You know how with RAID-5 you can lose any one drive and still recover? And there is also something called RAID-6 where you can lose any two drives and still recover. Erasure coding is the generalization of this pattern: you get to configure it for how many drives you could lose and still recover. Tahoe-LAFS is typically configured to upload each file to 10 different drives, where you can lose any 7 of them and still recover the entire file. This gives radically better reliability than typical RAID setups, at a cost of only 3.3 times the storage space that a single copy takes. + +Q: Where should I look for current documentation about Tahoe's protocols? + +