[tahoe-dev] [tahoe-lafs] #732: Not Enough Shares when repairing a file which has 7 shares on 2 servers

[tahoe-lafs]

#732: Not Enough Shares when repairing a file which has 7 shares on 2 servers
----------------------------+-----------------------------------------------
 Reporter:  zooko           |           Owner:  zooko
     Type:  defect          |          Status:  new  
 Priority:  major           |       Milestone:  1.5.0
Component:  code-encoding   |         Version:  1.4.1
 Keywords:  repair process  |   Launchpad_bug:       
----------------------------+-----------------------------------------------

Comment(by warner):

 Yeah, !MustForceRepairError is indicated for mutable files, when there are
 fewer than 'k' shares of some version N, but k or more shares of some
 version N-1. (the version numbers are slightly more complicated than that,
 but that's irrelevant). This means that the repairer sees evidence of a
 newer version, but is unable to recover it, and passing in force=True to
 the repair() call will knowingly give up on that version.

 I don't think there is yet a webapi to pass force=True. Also, I think
 there might be situations in which the repairer fails to look far enough
 for newer versions. Do a "check" and look at the version numbers (seqNNN
 in the share descriptions), to see if the message seems correct.

 This can occur when a directory update occurs while the node is not
 connected to the usual storage nodes, especially if the nodes that *are*
 available then go away later.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/732#comment:11>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid