[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 daira):

 Sorry, intended to paste the code:
 {{{
         if ((last_size != size
              or not use_timestamps
              or last_mtime != mtime
              or last_ctime != ctime) # the file has been changed
             or (not row2) # we somehow forgot where we put the file last
 time
             ):
             c.execute("DELETE FROM local_files WHERE path=?", (path,))
             self.connection.commit()
             return FileResult(self, None, False, path, mtime, ctime, size)
 }}}

 So when {{{not use_timestamps}}}, the existing db entry is deleted and the
 {{{FileResult}}} has {{{None}}} for the existing file URI. (Note that we
 still might not repair the file very well; see #1382.)

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