[FIXED] Filestore always use tombstone for recovered trailing deletes#7782
Merged
neilalexander merged 1 commit intomainfrom Feb 2, 2026
Merged
[FIXED] Filestore always use tombstone for recovered trailing deletes#7782neilalexander merged 1 commit intomainfrom
neilalexander merged 1 commit intomainfrom
Conversation
MauriceVanVeen
force-pushed
the
maurice/fs-index-skip-msg
branch
from
1823f69 to
87e604f
Compare
MauriceVanVeen
changed the title
MauriceVanVeen
force-pushed
the
maurice/fs-index-skip-msg
branch
from
87e604f to
b84c2d6
Compare
Signed-off-by: Maurice van Veen <github@mauricevanveen.com>
MauriceVanVeen
force-pushed
the
maurice/fs-index-skip-msg
branch
from
b84c2d6 to
77159a8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When restoring from a stale
index.dbstream state file, we still remember the last sequence that was used. If this last sequence was higher than is currently on disk, we move the recovered lower last sequence up to the highest seen last sequence. However, the last sequence and timestamp were adjusted even if no tombstone was actually written.Signed-off-by: Maurice van Veen github@mauricevanveen.com