[tahoe-dev] symlink to storage on a different drive and available space reporting

David-Sarah Hopwood david-sarah at jacaranda.org
Wed Jan 27 02:28:08 UTC 2010

Jody Harris wrote:
> So, we have several users who are storing the Tahoe shares on a drive other
> than where /home is located.
> Our strategy at this point is to simply delete the .tahoe/storage/shares
> directory and create a symlink to the desired storage location.
> This results in the available space reported as something completely
> unrelated to reality.
> Obviously, this is the wrong strategy. What does the tahoe-dev team
> recommend?

A server can be created in any directory using the --basedir option.
I think I'm also correct in saying that its files don't contain any paths
specific to its original location, so it should be possible to move them
anywhere and then run the server by specifying --basedir.
This is probably not well-enough documented.

David-Sarah Hopwood  ⚥  http://davidsarah.livejournal.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 292 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20100127/fdc0272d/attachment.asc>

More information about the tahoe-dev mailing list