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

Jody Harris imhavoc at gmail.com
Wed Jan 27 02:36:51 UTC 2010


If it is documented, I never saw it. I spent about two weeks reading Tahoe
docs before I installed.
----
- Think carefully.
- Contra mundum - "Against the world" (St. Athanasius)
- Credo ut intelliga - "I believe that I may know" (St. Augustin of Hippo)


On Tue, Jan 26, 2010 at 7:28 PM, David-Sarah Hopwood <
david-sarah at jacaranda.org> wrote:

> 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
>
>
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at allmydata.org
> http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20100126/857fdd63/attachment.html>


More information about the tahoe-dev mailing list