[tahoe-lafs-trac-stream] [tahoe-lafs] #1689: assertion failure

[tahoe-lafs]

#1689: assertion failure
-------------------------+-------------------------------------------------
     Reporter:  jg71     |      Owner:  zooko
         Type:  defect   |     Status:  closed
     Priority:           |  Milestone:  1.9.2
  critical               |    Version:  1.9.1
    Component:  code-    |   Keywords:  tahoe-check verify regression
  mutable                |  assertion error mutable review-needed
   Resolution:  fixed    |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by davidsarah):

 Before it was edited, comment:16 said:
 > I tested latest git and ran the same tests again. At first it looked ok,
 the weirdness was gone (that suddenly all dir caps show up as unhealthy).
 But after having re-run the repair job a few times with one storage node
 down, some aliases always show up completely healthy, and others show the
 weird behaviour again; all files are shown healthy but for those few
 aliases all dir caps are shown unhealthy, get repaired, and still show
 unhealthy while their repair was claimed to be successful:

  {{{
  *** test3
          '<root>': not healthy
           repair successful
          'test.txt': healthy
          done: 2 objects checked
           pre-repair: 1 healthy, 1 unhealthy
           1 repairs attempted, 1 successful, 0 failed
           post-repair: 1 healthy, 1 unhealthy

  *** test4
          '<root>': not healthy
           repair successful
          done: 1 objects checked
           pre-repair: 0 healthy, 1 unhealthy
           1 repairs attempted, 1 successful, 0 failed
           post-repair: 0 healthy, 1 unhealthy
  }}}

 The fact that caps were shown to be unhealthy even though they had been
 successfully repaired, sounds like ticket #766.

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