tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

add link to architecture doc 

[Imported from Trac: page FAQ, version 5]
davidsarah 2009-10-20 02:54:51 +00:00
parent 8e9ff6810d
commit 3a797234fb
1 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
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? 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. 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?
<http://allmydata.org/source/tahoe/trunk/docs/architecture.txt>