[tahoe-dev] [tahoe-lafs] #1212: Repairing fails if less than 7 servers available

tahoe-lafs trac at tahoe-lafs.org
Thu Oct 14 03:10:36 UTC 2010

#1212: Repairing fails if less than 7 servers available
     Reporter:  eurekafag     |       Owner:                            
         Type:  defect        |      Status:  reopened                  
     Priority:  major         |   Milestone:  1.8.1                     
    Component:  code-network  |     Version:  1.8.0                     
   Resolution:                |    Keywords:  reviewed regression repair
Launchpad Bug:                |  

Comment (by zooko):

 I think we should distinguish between levels of happiness at which the
 uploader or repairer will
  * (a) abort the upload or repair,
  * (b) treat the file as ''"unhealthy"'' which means
   * (b.1) a check-and-repair will trigger the repair step and
   * (b.2) a check results or a repair results will show the file (with
 clear, noticeable presentation) as being in danger ),
  * (c) treat the file as ''"perfectly healthy"'' which means that a repair
 would not make any change to it.

 One of the questions in this ticket -- comment:21 -- is whether (a) should
 trigger when {{{|M| < K}}} or not. Sometimes people would rather that the
 uploader/repairer get the file out there, even if all the shares are on a
 single server! Other times people might prefer that the uploader/repairer
 avoid wasting bandwidth on that and instead stop and raise the alarm.

 #614 is all about whether (b) should trigger when {{{|M| < N}}} (current
 behavior) or {{{|M| < H}}} (proposed new behavior).

Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1212#comment:22>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage

More information about the tahoe-dev mailing list