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

Comment (by srl):

 Replying to [comment:11 daira]:
 > Hmm, it looks from this code in the method {{{BackupDB_v2.check_file}}}
 in [source:src/allmydata/scripts/backupdb.py], as though the {{{--ignore-
 timestamps}}} option of {{{tahoe backup}}} causes existing db entries to
 be completely ignored, rather than only ignoring timestamps.
 >
 > Perhaps we just need to rename {{{--ignore-timestamps}}} or document it
 better?

 Just to note,  I had to both rename the db AND unlink the bad directories
 to get them repaired.

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