Opened at 2010-02-14T16:59:12Z
Closed at 2010-02-14T23:44:17Z
#949 closed defect (duplicate)
operation handle expired
Reported by: | zooko | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | undecided |
Component: | code-frontend | Version: | 1.6.0 |
Keywords: | reliability usability memory repair verify leases | Cc: | |
Launchpad Bug: |
Description
I just ran an important deep-check-and-repair, and when I came back to see what had happened I got "unknown/expired handle". This information is gone for good -- since the repair part repaired the files now there is now way for me to tell what their state was before the repair, which was information that I very much wanted to know.
I propose that operation handles be infinite duration by default, and people who want to save a few KB of virtual memory at the cost of risking losing information can configure their node to expire operation handles.
Change History (1)
comment:1 Changed at 2010-02-14T23:44:17Z by davidsarah
- Resolution set to duplicate
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
Duplicate of #577.