[tahoe-lafs-trac-stream] [tahoe-lafs] #2035: Publishing the same immutable content when some shares are unrecoverable does not repair that content.

[tahoe-lafs]

#2035: Publishing the same immutable content when some shares are unrecoverable
does not repair that content.
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  daira
  nejucomo               |     Status:  new
         Type:  defect   |  Milestone:  undecided
     Priority:  normal   |    Version:  1.10.0
    Component:  unknown  |   Keywords:  usability preservation reliability
   Resolution:           |  servers-of-happiness repair tahoe-backup
Launchpad Bug:           |  performance
-------------------------+-------------------------------------------------
Changes (by daira):

 * keywords:
     usability preservation reliability servers-of-happiness repair tahoe-
     backup
     =>
     usability preservation reliability servers-of-happiness repair tahoe-
     backup performance


Comment:

 The backupdb is a performance hack to avoid the latency cost of asking
 servers whether each file exists on the grid. If the latter were fast
 enough (which would probably require batching requests for multiple
 files), then it wouldn't be needed. ({{{tahoe backup}}} probabilistically
 checks some files on each run even if they are present in the backupdb,
 but I don't think that particularly helps.)

 In the meantime, how about adding a {{{--repair}}} option to {{{tahoe
 backup}}}, which would bypass the backupdb and upload/repair every file?

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