Thanks Brian,<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div bgcolor="#FFFFFF"><div>We could also bring sizelimit= back as is, with a warning that it may take a long time to reatart the node when there are a lot of shares.</div>
<div></div></div></blockquote><div><br>Yes please, as without it the volunteers grid will not be an option for a number of people, including me.<br><br>I am assuming it should be easy to bypass space checks completely, when the variable sizelimit= is not set, so it should not have negative impact on anyone not specifying a value there.<br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div bgcolor="#FFFFFF"><div>Or, the Accounting work I'm slowly accomplishing in the background would provide a more fine-grained limit, and would include a coarse server-wide limit as a side-effect.</div>
</div></blockquote><div><br>Which sounds great, but with unknown delivery date. BTW, how is that going, I'm hoping the linked data privacy issue can be resolved when Accounting work is done?<br><br>Thanks,<br>Andrej Falout<br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div bgcolor="#FFFFFF"><div></div><div></div><div>Hope that helps,</div><div> -Brian</div>
<div><div></div><div class="Wj3C7c"><div><br></div><div><br>On Mar 1, 2009, at 1:44 AM, Rogério Schneider <<a href="mailto:stockrt@gmail.com" target="_blank">stockrt@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite">
<div>Andrej, what you want is 'sizelimit'. This configuration limits the utilization of<br>storage for a given client.<br><br>To share only 2GB, for example:<br><br>[storage]<br>enabled = true<br>sizelimit = 2000000000<br>
<br><a href="http://allmydata.org/source/tahoe/trunk/docs/configuration.txt" target="_blank"></a><a href="http://allmydata.org/source/tahoe/trunk/docs/configuration.txt" target="_blank">http://allmydata.org/source/tahoe/trunk/docs/configuration.txt</a><br>
<br>Regards,<br>Rogério Schneider<br><br><br><div class="gmail_quote">On Sun, Mar 1, 2009 at 3:09 AM, Andrej Falout <span dir="ltr"><<a href="mailto:andrej@falout.org" target="_blank"></a><a href="mailto:andrej@falout.org" target="_blank">andrej@falout.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Thanks Rogério,<div><br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
That 'reserved_space' is, as documented, the minimum space tahoe will try to keep free in your disk. Say, when you disk goes to only 2gb (in my config) it will stop storing new chunks. This is exactly what you want.<br>
</blockquote></div><br></div>Unless I'm missing something, not exactly.<br><br>On my 3T mount, this would consume all space between currently used 1T and (3T-2G)<br><br clear="all">I'd like to allocate only a portion of (3T-2G) to Tahoe storage, as I will need it in the future. <br>
<br>therefor the need for something like storage_use_max=xxxx parameter.<br><br>IIUC, reserved_space= has the meaning of "dont store any more data if partition space is less then this"<br><br>I would like to be able to declare "use maximum x MB, but only if doing so will not reduce available space under y MB"<br>
<br>-- <br><font color="#888888">Andrej Falout<br><br>
</font><br>_______________________________________________<br>
tahoe-dev mailing list<br>
<a href="mailto:tahoe-dev@allmydata.org" target="_blank"></a><a href="mailto:tahoe-dev@allmydata.org" target="_blank">tahoe-dev@allmydata.org</a><br>
<a href="http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev" target="_blank"></a><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></blockquote></div><br><br>-- <br>Rogério Schneider<br><br>MSN: <a href="mailto:stockrt@hotmail.com" target="_blank"></a><a href="mailto:stockrt@hotmail.com" target="_blank">stockrt@hotmail.com</a><br>GTalk: <a href="mailto:stockrt@gmail.com" target="_blank"></a><a href="mailto:stockrt@gmail.com" target="_blank">stockrt@gmail.com</a><br>
TerraVoip: stockrt<br>
Skype: stockrt<br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>tahoe-dev mailing list</span><br><span><a href="mailto:tahoe-dev@allmydata.org" target="_blank">tahoe-dev@allmydata.org</a></span><br>
<span><a href="http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev" target="_blank">http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev</a></span><br></div></blockquote></div></div></div><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>
<br></blockquote></div><br><br clear="all"><br>-- <br>Andrej Falout<br>AU: +61 (410) 463 735 NZ: +64 (21) 0256 6825 US: +1 (360) 488 0970<br>