[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:           |
-------------------------+-------------------------------------------------

Comment (by srl):

 Replying to [comment:5 nejucomo]:
 > Therefore I propose this is a bug in backupdb caching logic.  If
 possible it should verify the health of items in the cache.  If this is
 expensive, maybe it could be an opt-in behavior with a commandline option.

 backup-and-verify would be nice. I would think that backup could be
 efficient here, simply check if the shares are there before re-using its
 cache.

 Also note the trick is to nuke the database AND unlink. So that trick
 probably can't work with preserving the Archived items.

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