Re: [tahoe-dev] tahoe -d is awkward

2011-05-11 Thread Brian Warner
On 4/6/11 3:29 PM, Greg Troxel wrote: > > So, I find myself doing > > tahoe deep-check -d ~/.tahoe-gdt --add-lease --repair > tahoe deep-check -d ~/.tahoe-pubgrid --add-lease --repair > > and naturally would like to have aliases > > tahoep () { tahoe -d ${HOME}/.tahoe-pubgrid $*; } > tahoeg

Re: [tahoe-dev] Mixing different shares.needed/happy/total settings

2011-05-11 Thread Zooko O'Whielacronx
On Tue, May 3, 2011 at 8:00 AM, Lionel Bouton wrote: > > First, thanks for an amazing piece of software You're welcome! Thanks for the encouragement! > and thanks to the people > packaging it for Gentoo: I thought I'll spend quite some time reading > docs and Python code but the installation an

Re: [tahoe-dev] Storage Node Proactive Share Relocation

2011-05-11 Thread Zooko O'Whielacronx
On Wed, May 11, 2011 at 12:36 PM, Brian Warner wrote: > > Yeah, you don't even have to regenerate anything, just copy. This is true for immutable shares, but not for mutable shares. Mutable shares include a token called the "write authenticator" which is used by the client to prove that it has th

Re: [tahoe-dev] Mixing different shares.needed/happy/total settings

2011-05-11 Thread Brian Warner
On 5/3/11 7:00 AM, Lionel Bouton wrote: > > 1/ If I understand correctly, at least "needed" and "total" are only > used when creating new content (file-encoding.rst: « the encoding > parameters are included in the hash stored »). But is the "happy" > value stored too or read from conf ? IE: will a

Re: [tahoe-dev] Storage Node Proactive Share Relocation

2011-05-11 Thread Brian Warner
On 5/11/11 11:13 AM, Greg Troxel wrote: > > Nathan Eisenberg writes: > >> However, if you've got valid shares on that server, why not be able to >> use them to regenerate shares? In other words, have the storage node >> reallocate its own shares before making them unavailable. Yeah, you don't

Re: [tahoe-dev] Storage Node Proactive Share Relocation

2011-05-11 Thread Greg Troxel
Nathan Eisenberg writes: > I got to wondering last night... say you have a grid that you're > removing a storage node from for one reason or another. In my mind, > the current correct procedure would be to run a repair-walk through > all the known DIRCAPs, to ensure everything is in a good stat

[tahoe-dev] Storage Node Proactive Share Relocation

2011-05-11 Thread Nathan Eisenberg
Hi all, I got to wondering last night... say you have a grid that you're removing a storage node from for one reason or another. In my mind, the current correct procedure would be to run a repair-walk through all the known DIRCAPs, to ensure everything is in a good state to start with, then st