Tahoe-LAFS: Difference between revisions
imported>Mjh |
imported>Mjh No edit summary |
||
| Line 107: | Line 107: | ||
===How come there are no mountable filesystem frontends?=== | ===How come there are no mountable filesystem frontends?=== | ||
There are; they just aren't built-in. Tahoe's high latency makes it rather unwieldy for use as part of a conventional filesystem. Append operations in particular are extremely inefficient. It is recommended that you use the web and CLI interfaces to manage files stored in tahoe. | There are; they just aren't built-in. Tahoe's high latency makes it rather unwieldy for use as part of a conventional filesystem. Append operations in particular are extremely inefficient. It is recommended that you use the web and CLI interfaces to manage files stored in tahoe. | ||
===What are the downsides?=== | |||
Currently there's a reliance on a central introducer. This has several disadvantages: | |||
* If the introducer goes away, every node in the system must be reconfigured to choose a new introducer furl string. | |||
* Tahoe's erasure coding maintains availability in the event of a loss of nodes, but not malicious nodes. It's trivial to DoS a grid either by a Sybil attack or just using up all available storage if you know the introducer furl string. A [https://tahoe-lafs.org/trac/tahoe-lafs/ticket/467 patch] is in the works to allow clients to choose their own storage nodes that should mitigate this. | |||
[[Category:VTLUUG Projects]] | [[Category:VTLUUG Projects]] | ||
[[Category:Infrastructure]] | [[Category:Infrastructure]] | ||
[[Category:Software]] | [[Category:Software]] | ||