Since I'm not going to ask my users to change the code, I'm going to go with linking to storage rather than shares.<div><br></div><div>Thanks!</div><div><br></div><div>Jody<br clear="all">----<br>- Think carefully.<br>
- Contra mundum - "Against the world" (St. Athanasius)<br>- Credo ut intelliga - "I believe that I may know" (St. Augustin of Hippo)<br>
<br><br><div class="gmail_quote">On Tue, Jan 26, 2010 at 10:24 AM, David Triendl <span dir="ltr"><<a href="mailto:david@triendl.name">david@triendl.name</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Tue, Jan 26, 2010 at 09:34:00AM -0700, Jody Harris wrote:<br>
> So, we have several users who are storing the Tahoe shares on a drive other<br>
> than where /home is located.<br>
</div>I have a similar strategy, placing the node data in /var/lib/tahoe and the<br>
shares on a drive mounted at /srv/gridname, and I don't have any problem:<br>
<br>
david@mimir:/var/lib/tahoe/testgrid$ ls -l storage<br>
lrwxrwxrwx 1 root root 20 Jan 16 18:18 storage -> /srv/tahoe/testgrid/<br>
david@mimir:/var/lib/tahoe/testgrid$ df -h . storage<br>
Filesystem Size Used Avail Use% Mounted on<br>
/dev/mapper/sda3_crypt<br>
14G 2.0G 12G 16% /<br>
/dev/mapper/mimir-testgrid<br>
2.0G 699M 1.4G 35% /srv/tahoe/testgrid<br>
david@mimir:/var/lib/tahoe/testgrid$ wget -O - -q <a href="http://mimir:3567/storage" target="_blank">http://mimir:3567/storage</a> | grep -A 1 "free (r"<br>
<tr><td>Disk space free (root):</td><br>
<td>1.40 GB</td><br>
<br>
As you can see, the only difference is, that I link storage/ to a different<br>
location, while you link storage/shares. A look at the code<br>
(src/allmydata/storage/server.py) confirms it: There are two directories, one<br>
called the "storedir" (storage/), which the statvfs-call is called for, and the<br>
"sharedir" (storage/shares) which holds the actual shares.<br>
<br>
As you can see, the fix is easy: (src/allmydata/storage/server.py, around line<br>
151) replace "disk_avail = self.stat_disk(self.storedir)" with "disk_avail =<br>
self.stat_disk(self.sharedir)", or change the symlink to link storage/ instead<br>
of storage/shares/.<br>
<br>
Cheers,<br>
David<br>
<div class="im"><br>
<br>
><br>
> Our strategy at this point is to simply delete the .tahoe/storage/shares<br>
> directory and create a symlink to the desired storage location.<br>
><br>
> This results in the available space reported as something completely<br>
> unrelated to reality.<br>
><br>
> Obviously, this is the wrong strategy. What does the tahoe-dev team<br>
> recommend?<br>
><br>
> thanks,<br>
> Jody<br>
> ----<br>
> - Think carefully.<br>
> - Contra mundum - "Against the world" (St. Athanasius)<br>
> - Credo ut intelliga - "I believe that I may know" (St. Augustin of Hippo)<br>
<br>
</div>> _______________________________________________<br>
> tahoe-dev mailing list<br>
> <a href="mailto:tahoe-dev@allmydata.org">tahoe-dev@allmydata.org</a><br>
> <a href="http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev" target="_blank">http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev</a><br>
<br>
_______________________________________________<br>
tahoe-dev mailing list<br>
<a href="mailto:tahoe-dev@allmydata.org">tahoe-dev@allmydata.org</a><br>
<a href="http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev" target="_blank">http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev</a><br>
</blockquote></div><br></div>