Opened at 2010-09-23T23:38:26Z
Last modified at 2013-06-18T00:49:19Z
#1209 assigned defect
repair of immutable files should not increment the sequence number — at Initial Version
Reported by: | gdt | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | soon |
Component: | code-mutable | Version: | 1.8.0 |
Keywords: | repair mutable preservation space-efficiency | Cc: | |
Launchpad Bug: |
Description
I often find that 9 shares of seqN are available compared to 10 desired. I do a repair, and this results in 10 shares of seqN+1 and then 9 are deleted. Then the next day there are 9 of seqN+1 and 1 of seqN, and the file is again not healthy. This repeats daily.
It seems that the missing seqN shares should be generated and placed, and then when servers churn more it's likely that 10 can still be found, and no unrecoverable versions. Perhaps I don't get something, but the current behavior is not stable with intermittent servers.
Note: See
TracTickets for help on using
tickets.