Opened at 2010-09-23T23:38:26Z

Last modified at 2013-06-18T00:49:19Z

#1209 assigned defect

repair of directories (all immutable files) should not increment the sequence number — at Version 2

Reported by: gdt Owned by: gdt
Priority: major Milestone: soon
Component: code-mutable Version: 1.8.0
Keywords: repair mutable preservation space-efficiency Cc:
Launchpad Bug:

Description (last modified by gdt)

Particularly with my root directory, 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.

Change History (2)

comment:1 Changed at 2010-09-29T12:22:35Z by zooko

  • Owner changed from somebody to gdt
  • Version changed from 1.8β to 1.8.0

gdt: did you mean "mutable" instead of "immutable"? Immutable files don't have a sequence number!

comment:2 Changed at 2010-09-29T13:35:29Z by gdt

  • Description modified (diff)
  • Summary changed from repair of immutable files should not increment the sequence number to repair of directories (all immutable files) should not increment the sequence number

Sorry, I really meant directories in particular. I have edited the summary and description.

Note: See TracTickets for help on using tickets.