[tahoe-lafs-trac-stream] [tahoe-lafs] #1566: if a stored share has a corrupt header, other shares held by that server for the file should still be accessible to clients

[tahoe-lafs]

#1566: if a stored share has a corrupt header, other shares held by that server
for the file should still be accessible to clients
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  warner
  davidsarah             |     Status:  new
         Type:  defect   |  Milestone:  1.10.0
     Priority:  major    |    Version:  1.9.0b1
    Component:  code-    |   Keywords:  corruption preservation storage
  storage                |  design-review-needed zookos-opinion-wanted
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by davidsarah):

 Replying to [comment:4 davidsarah]:
 > Replying to [comment:3 warner]:
 > > I think the server should not report anything to the client about
 shares with corrupt headers. It should file a local corruption report (as
 if the remote client had called {{{remote_advise_corrupt_share()}}}, but
 with a flag that shows this was discovered locally, and probably in a part
 of the share that the client wouldn't be able to read anyways).
 > [...]
 >
 > Good, that's essentially what I'd implemented in
 [5477/ticket999-S3-backend].

 ... except for filing a corruption report, which I agree is a good idea.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1566#comment:6>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage