[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:  nejucomo  |          Owner:  daira
     Type:  defect    |         Status:  new
 Priority:  normal    |      Milestone:  undecided
Component:  unknown   |        Version:  1.10.0
 Keywords:            |  Launchpad Bug:
----------------------+---------------------------
 From `srl295` on IRC:

     Interesting behavior- Had some stuff on our grid backed up with 'tahoe
 backup'  which creates Latest, Archive etc- some of them are immutable
 dirs.   Then, I lost a drive.  So that particular storage node went down
 and never came back.   Some directories were irrecoverable, OK fine. I
 create new directories and run tahoe backup again on the new directory
 URI.    However, I'm still getting errors on deep check. - ERROR:
 NotEnoughSharesError(ran out of shares: complete= pending=Share(sh1-on-
 sslg5v) overdue= unused= need 2. Last failure: None)   -- I wonder, is
 tahoe reusing some unrecoverable URIs since the same immutable directory
 was created?

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