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

[tahoe-lafs]

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

Comment (by jg71):

 I applied fix-1689.diff and the error is gone. But I noticed the following
 while running "tahoe deep-check -v --repair --add-lease alias:"

 - if one storage server is shut down, every dir cap (incl. root) is marked
 unhealthy and repaired, as are all files, except lit caps which are shown
 healthy

 - if all servers are online, by default all dir caps are marked unhealthy
 and repaired but not quite:

 {{{
 done: 4 objects checked
  pre-repair: 3 healthy, 1 unhealthy
  1 repairs attempted, 1 successful, 0 failed
  post-repair: 3 healthy, 1 unhealthy
 }}}

 The unhealthy one is the dir root cap. Another alias which includes a
 directory shows the same behaviour:

 {{{
 done: 69 objects checked
  pre-repair: 0 healthy, 69 unhealthy
  69 repairs attempted, 69 successful, 0 failed
  post-repair: 67 healthy, 2 unhealthy
 }}}

 Noteworthy is the fact that lit caps always show up as healthy, if all
 servers are there or one missing.

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