[tahoe-dev] odd repair output

David-Sarah Hopwood david-sarah at jacaranda.org
Mon Mar 18 04:48:45 UTC 2013


On 16/03/13 13:52, Greg Troxel wrote:
>   I wonder if the repair should not be attempted unless there are enough
>   servers online to make the end-state possibly better than the
>   beginning state.

The algorithm I gave in
<https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1212#comment:14>
does that.

>   Probably the definition of "repair successful" should align better
>   with post-repair being "healthy".

Yes, that's <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/614>.

>   I wonder how much of this will go away if extra shares are placed
>   without version number changes in these kinds of situations.

It may reduce the incidence for mutable files/directories, but we need
to make these fixes to the repair algorithm anyway.

-- 
David-Sarah Hopwood ⚥

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


More information about the tahoe-dev mailing list