Tahoe-LAFS: Difference between revisions
imported>Mjh No edit summary |
imported>Pew No edit summary |
||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
Tahoe-LAFS is a distributed filesystem which provides redundancy and security for files. | Tahoe-LAFS is a distributed filesystem which provides redundancy and security for files. Our most recent incarnation was run on [[Infrastructure:Crashoverride|Crashoverride]] | ||
==Connecting to VTLUUG's Tahoe Grid== | ==Connecting to VTLUUG's Tahoe Grid== | ||
| Line 11: | Line 11: | ||
** Available in Arch's community repo | ** Available in Arch's community repo | ||
* Install various dependencies. | * Install various dependencies. | ||
** On | ** On Debian 9, install <code>python-txtorcon tahoe-lafs tor</code> | ||
* | ** On Debian 8, the distro packages are too old so you need to install things manually. | ||
* | *** <code>pip2 install -U pyopenssl txtorcon tahoe-lafs</code> | ||
*** Follow the Tor Project's [https://www.torproject.org/docs/debian.html.en instructions] for installing the latest stable version of tor on Debian Jessie. | |||
** CentOS 6 is unsupported, as Tahoe-LAFS now requires Python 2.7. | |||
* | * Edit <code>/etc/tor/torrc</code> and uncomment the <code>ControlPort 9051</code> line, then restart tor. | ||
* Edit the tahoe defaults file (<code>/etc/defaults/tahoe-lafs</code>) to start your nodes along with tahoe-lafs startup. Note that in this example, I have two node directories underneath "/srv/tahoe-storage", "introducer" and "tor-storage". For most users you should only have one node directory for storage. | |||
<pre> | |||
* | # Start only these tahoe-lafs nodes automatically via init script. Allowed | ||
# values are "all", "none" or space separated list of tahoe-lafs nodes. If | |||
# empty, "none" is assumed. | |||
# | |||
#AUTOSTART="all" | |||
AUTOSTART="introducer tor-storage" | |||
#AUTOSTART="home office" | |||
# Pass arguments to tahoe start. Default to "--syslog". | |||
DAEMONARGS="--syslog" | |||
CONFIG_DIR="/srv/tahoe-storage" | |||
</pre> | |||
* Create a Tahoe user and add it to the tor group | |||
** <code>useradd tahoe-lafs</code> | |||
** <code>usermod -aG debian-tor tahoe-lafs</code> | |||
* Create the appropriate tahoe services, and start them: | |||
** <code>sudo -u tahoe-lafs tahoe create-node --listen=tor -n YOUR_NODE_NAME -C /srv/tahoe-storage/vtluug-tor-storage -i GET_THIS_STRING_FROM_AN_OFFICER</code> | |||
** <code>systemctl start tahoe-lafs</code> | |||
* | |||
=== Tuning === | === Tuning === | ||
| Line 59: | Line 49: | ||
==Troubleshooting== | ==Troubleshooting== | ||
This is a list of various problems I've encountered. --[[User:Mjh|Mjh]] ([[User talk:Mjh|talk]]) 00:47, 30 December 2014 (EST) | This is a list of various problems I've encountered. --[[User:Mjh|Mjh]] ([[User talk:Mjh|talk]]) 00:47, 30 December 2014 (EST) | ||
=== | === Tahoe daemonized and then terminated immediately === | ||
This can be caused by several factors when running with torsocks. | This can be caused by several factors when running with torsocks. | ||
* You're trying to bind to an IP other than localhost and torsocks blocked this | * You're trying to bind to an IP other than localhost and torsocks blocked this. Ensure the tub.port and web.port lines are set to restrict traffic to localhost. | ||
* Tahoe is attempting to establish a UDP connection to identify its local IP address. Torsocks restricts UDP connections, causing Tahoe to throw exceptions and terminate. Ensure you are using the [https://github.com/tahoe-lafs/tahoe-lafs latest trunk version] rather than the version supplied by your OS. | |||
* Tahoe is attempting to establish a UDP connection to identify its local IP address. Torsocks restricts UDP connections, causing Tahoe to throw exceptions and terminate. | === Can't connect to introducer === | ||
* Ensure tor is running and that Tahoe is started through torify. | |||
* Ensure the <code>introducer.furl</code> parameter is not enclosed with quotes in <code>tahoe.cfg</code>. For some reason this has caused connection issues for me. | |||
==FAQs== | ==FAQs== | ||
Technical documentation on | Technical documentation on Tahoe can be found on its website. However, for the prospective user, here's a simple explanation in Q&A format: | ||
===What does it do?=== | ===What does it do?=== | ||
| Line 91: | Line 83: | ||
===How do I delete files?=== | ===How do I delete files?=== | ||
You can't. The nodes are not trusted and therefore cannot be relied upon to remove the file's shares when asked. To render a file inaccessible, destroy all copies of the filecap. After | You can't. The nodes are not trusted and therefore cannot be relied upon to remove the file's shares when asked. To render a file inaccessible, destroy all copies of the filecap. After 60 days, the file's lease will expire and its shares will be automatically garbage collected, or deleted, by the nodes. | ||
===Wait, files expire? But I thought...=== | ===Wait, files expire? But I thought...=== | ||
VTLUUG's grid uses a 2 month file lease to prevent the grid from filling up permanently. | |||
Don't panic. To stop a file from being deleted after 2 months, simply renew its lease. The recommended way of doing this is setting up an alias using tahoe create-alias tahoe, adding the filecap to the alias, and setting up a weekly cronjob to run tahoe deep-check --renew tahoe. This will renew the leases on all the files in the alias, which is similar to a directory. | |||
===Directory?=== | ===Directory?=== | ||
| Line 104: | Line 96: | ||
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?=== | ||
[[Category: | Currently there's a reliance on a central introducer. This has several disadvantages: | ||
[[Category: | * 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:Deprecated]] | |||