[tahoe-lafs-trac-stream] [tahoe-lafs] #2026: storage server should file a local corruption report if it discovers a share with a corrupted container

[tahoe-lafs]

#2026: storage server should file a local corruption report if it discovers a
share with a corrupted container
------------------------------+------------------------
 Reporter:  daira             |          Owner:
     Type:  defect            |         Status:  new
 Priority:  normal            |      Milestone:  soon
Component:  code-storage      |        Version:  1.10.0
 Keywords:  error corruption  |  Launchpad Bug:
------------------------------+------------------------
 This ticket concerns the behaviour of a storage server for shares where
 the container is corrupt.

 In ticket:1566#comment:3 , Brian wrote:
 > 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).

 See also #2025.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2026>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage