[tahoe-dev] [tahoe-lafs] #812: server-side crawlers: tolerate corrupted shares, verify shares (was: handle corrupted lease files)

[tahoe-lafs]

#812: server-side crawlers: tolerate corrupted shares, verify shares
--------------------------+-------------------------------------------------
 Reporter:  zooko         |           Owner:  warner   
     Type:  defect        |          Status:  new      
 Priority:  major         |       Milestone:  undecided
Component:  code-storage  |         Version:  1.4.1    
 Keywords:                |   Launchpad_bug:           
--------------------------+-------------------------------------------------

Comment(by warner):

 Sounds good. To be specific, this is unrelated to leases, it's just that
 the lease-expiring crawler is what first noticed the corruption. So this
 ticket is about:

  * verify that the crawlers keep crawling after an exception in their per-
 share handler functions (I believe that it already does this, but we
 should verify it)
  * implement a share-verifying crawler (the server-side verifier), and
 have it quarantine any corrupted share in some offline junkpile

 And yeah, just rm the file, it's useless to anyone. The next time that
 directory is modified, a new copy of that share will be created.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/812#comment:4>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid