-
Notifications
You must be signed in to change notification settings - Fork 140
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
Getting 'entered unreachable code' panic from btree_mutator after interrupting casey/ord #515
Comments
Well that's definitely a bug! :/ I'll try to reproduce this. What command line options did you pass to ord when it hung? |
I did not pass any command line arguments. I have a collection of large ord index.redb files. I documented some of them in https://github.com/casey/ord/issues/1471. I can upload them to a service you point to. |
I think this is very likely fixed by #516 . That PR fixes a very bad data corruption bug in databases greater than ~4GB is size. Can you try running with the latest master? |
Thanks @cberner, I'll try! I've read https://github.com/cberner/redb/pull/516/files. It seems like this fix can work with "corrupted" databases, right? |
Not really. There's no way to fix the corruption unfortunately, so while it might allow you to open the database (which I'm going to disallow in #518) the database will still be corrupted. You'll need to delete the ord database and rebuild it |
The fix works fine for now. |
Ord had indexed 300k blocks with this for now. Thanks a lot @cberner! |
I interrupted @casey's ord (10f866) because it was stuck while indexing. I cannot start ord anymore due to a panic from redb-0.12.1:
redb is supposed to be "crash-safe by default", so I'm opening the issue here.
I'm running macOS Ventura on a Xeon processor with ECC RAM.
The text was updated successfully, but these errors were encountered: