Actions
Feature #453
closedosd: return error (instead of blocking) on lost objects
% Done:
0%
Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
We now track unfound objects. If we decide those objects are truly lost, we need to return errors when trying to read them.
We may also want to record their LOST status on disk in placeholder objects so that we can allow last_complete to move forward. Otherwise their unfound/lost state is tied to the missing/unfound sets, and incurs permanent peering/recovery overhead going forward.
Updated by Sage Weil over 13 years ago
- Target version changed from v0.23 to v0.24
Updated by Sage Weil over 13 years ago
- Estimated time set to 4:00 h
- Source set to 3
Updated by Sage Weil over 13 years ago
- Subject changed from osd: handle LOST_REVERT to osd: return error (instead of blocking) on lost objects
Updated by Colin McCabe over 13 years ago
- Status changed from New to Resolved
It's passing the lost1 and lost2 unit tests now.
Updated by Sage Weil over 13 years ago
- Translation missing: en.field_position deleted (
374) - Translation missing: en.field_position set to 339
Updated by Sage Weil over 13 years ago
- Translation missing: en.field_position deleted (
339) - Translation missing: en.field_position set to 301
Actions