[tahoe-lafs-trac-stream] [tahoe-lafs] #1209: repair of mutable files/directories should not increment the sequence number

[tahoe-lafs]

#1209: repair of mutable files/directories should not increment the sequence
number
-------------------------+-------------------------------------------------
     Reporter:  gdt      |      Owner:  davidsarah
         Type:  defect   |     Status:  assigned
     Priority:  major    |  Milestone:  1.11.0
    Component:  code-    |    Version:  1.8.0
  mutable                |   Keywords:  repair mutable preservation space-
   Resolution:           |  efficiency
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by PRabahy):

 I believe that davidsarah's algorithm should help for most cases. Does it
 make sense to use a vector clock
 (http://en.wikipedia.org/wiki/Vector_clock) for even more robustness. I
 don't believe this should happen often (ever), but if there is a partial
 brain split where several nodes can connect to more than S storage servers
 but less than half the total storage servers in the grid there could still
 be significant churn. (Did that last sentence make any sense?) I'm
 probably over-thinking this solution so feel free to ignore me.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1209#comment:20>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage