-
Notifications
You must be signed in to change notification settings - Fork 20.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
core/rawdb: fix cornercase shutdown behaviour in freezer #26485
Merged
Merged
Changes from 1 commit
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
f39e8df
core/rawdb: debug print exact numbers without prettification
holiman ebe49f4
core/rawdb: handle sync after close
holiman 3806472
core/rawdb: fix testcase, fix closed-check
holiman afd2457
core/rawdb: more verbosity after repair truncates items
holiman 63f7fba
cmd/geth: simplify freezer-inspect
holiman 40ede55
core/rawdb: fsync when closing freezer files
holiman 33b075c
core/rawdb: avoid sync on readonly files
holiman 743d702
core/rawdb: fixes re syncing files
holiman File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
cmd/geth: simplify freezer-inspect
- Loading branch information
commit 63f7fbaf28a1215f091489177427077fc3d8fc41
There are no files selected for viewing
This file contains 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
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any particular reason for this change? Directly resolve ancient datadir without involving the chain DB?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, for the investigation here: #26483 (comment) , I needed to do a
geth db inspect
, but I didn't actually have a leveldb -- I only had a couple of index files.This whole
utils.MakeChainDatabase
assumes things to be pretty well ordered, but all we use it for eventually is to help resolve the ancientdir, viadb.AncientDir
.So this change has the same effect as the original code, but is more robust in case the data is not fully consistent / present.