#874 closed defect (fixed)
Repairer raises MustForceRepairError in cases where it shouldn't
| Reported by: | davidsarah | Owned by: | nobody |
|---|---|---|---|
| Priority: | major | Milestone: | 1.6.0 |
| Component: | code-mutable | Version: | 1.5.0 |
| Keywords: | repair preservation news-done | Cc: | |
| Launchpad Bug: |
Description
Brian wrote in #786:
I found a bug in the repairer that incorrectly classifies an unrecoverable-but-not-completely-gone file (i.e. one with 1 or 2 shares, when k=3). It raises a MustForceRepairError with an explanation about there being unrecoverable newer versions. The intention was to raise this error when e.g. there are 9 shares of version 1, and 2 shares of version 2, since in that situation, repairing the only recoverable version (1) will knowingly discard the remaining shares of version 2, abandoning any hope of recovering the current contents of the file.
Change History (2)
comment:1 Changed at 2009-12-29T23:43:31Z by warner
- Component changed from unknown to code-mutable
- Milestone changed from undecided to 1.6.0
- Resolution set to fixed
- Status changed from new to closed
comment:2 Changed at 2010-02-02T05:53:31Z by davidsarah
- Keywords news-done added
Note: See
TracTickets for help on using
tickets.
ba0690c9d7a3bc28 fixes this, and returns results with successful=False when there are insufficient shares for repair and there is only one version visible.