[tahoe-lafs-trac-stream] [tahoe-lafs] #1628: UCWE on deep check with recent version

[tahoe-lafs]

#1628: UCWE on deep check with recent version
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  kevan
  davidsarah             |     Status:  closed
         Type:  defect   |  Milestone:  1.9.2
     Priority:           |    Version:  1.9.0
  critical               |   Keywords:  tahoe-check verify ucwe regression
    Component:  code     |  review-needed
   Resolution:  fixed    |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by amir):

 Hi all,

 I'm a tahoe-lafs novice, but playing with my first shares (4 storage
 servers, 2 clients on 2 of the storage servers, k=2, H=4, N=5) I succeeded
 within short time frame to fuckup my shares. I'm not yet fully sure what
 we did to confuse them, but in the end we had one share of seq2 and 5
 shares of seq10. A deep-check --repair alias: always resulted in this:

 $ tahoe deep-check --repair -v sound:28C3
 '<root>': not healthy[[BR]]
 repair successful[[BR]]
 '28c3.Pausenmusik.mp3': healthy[[BR]]
 done: 2 objects checked[[BR]]
 pre-repair: 1 healthy, 1 unhealthy[[BR]]
 1 repairs attempted, 1 successful, 0 failed[[BR]]
 post-repair: 1 healthy, 1 unhealthy

 It was always the mutable files which became unhealty. And no number of
 repairs could get them fixed.

 jg71 sugested to use git head, as some bugs were fixed there. I did as
 proposed and just found out that git head fixes all the above problems
 without fuss. Great work guys!

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