fix: panic when using large storage volumes and tombstone log - #1308
Open
zachgrayio wants to merge 3 commits into
Open
fix: panic when using large storage volumes and tombstone log#1308zachgrayio wants to merge 3 commits into
zachgrayio wants to merge 3 commits into
Conversation
zachgrayio
changed the title
Signed-off-by: Stax124 <novaktomas124@proton.me> Signed-off-by: Zach Gray <zgray@adobe.com>
Signed-off-by: Zach Gray <zgray@adobe.com>
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.
truncation because of accidental u32 cast here in tombstone logic caused panics on startup when using exact multiples of 1TiB or eventually after operation if not exact multiple of 1TiB when tombstone is enabled and large cache size is used