Opened at 2013-07-17T13:23:19Z

Last modified at 2021-03-30T18:40:19Z

#2026 new defect

storage server should file a local corruption report if it discovers a share with a corrupted container

Reported by: daira Owned by:
Priority: normal Milestone: soon
Component: code-storage Version: 1.10.0
Keywords: error corruption Cc:
Launchpad Bug:

Description

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.

Change History (5)

comment:1 Changed at 2014-12-06T14:47:53Z by daira

  • Milestone changed from soon to 1.12.0

comment:2 Changed at 2016-03-22T05:02:25Z by warner

  • Milestone changed from 1.12.0 to 1.13.0

Milestone renamed

comment:3 Changed at 2016-06-28T18:17:14Z by warner

  • Milestone changed from 1.13.0 to 1.14.0

renaming milestone

comment:4 Changed at 2020-06-30T14:45:13Z by exarkun

  • Milestone changed from 1.14.0 to 1.15.0

Moving open issues out of closed milestones.

comment:5 Changed at 2021-03-30T18:40:19Z by meejah

  • Milestone changed from 1.15.0 to soon

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.