[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:  soon
    Component:  code-    |    Version:  1.8.0
  mutable                |   Keywords:  repair mutable preservation space-
   Resolution:           |  efficiency
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by davidsarah):

 Greg Troxel wrote:
 > More than that - if we have 1 share of M and  all shares of N, for N >
 M, then we really just want to purge (or ignore?) the M share, and not
 molest the N shares.

 > The test for this should be like:
 {{{
   set up 5 servers S
   upload some files
   while 20 iterations
     for s in S
       take s off line
       run repair
       take s back
 }}}

 > With the current code, you get repair every time and 100 increments, I
 think.  With your proposal, I think it's still true.

 > The above test is how the pubgrid feels to me, or used to.

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