-
Notifications
You must be signed in to change notification settings - Fork 74
Error: Corruption: not an sstable (bad magic number) - Leveldb error #274
Comments
checking in.. That's my error!-) |
Meije, is this data yours? I ask, because I wrote a tool that leverages the leveldown repair() method. I'm not exactly sure if it will fix the problem (Because I don't have the problem, I can't run it to see if it can fix it) But if you have a system that has this error, I could provide instructions on how to run it and you can see if it will work. Note, that it could also destroy everything since I don't yet know what it is doing. So I would prefer to have it only used as a last resort for testing. Give me a shout if you want to try it. |
@tempestb , nope this is not my error, its from a user on rocketchat. |
I am having this issue as well on some of my nodes. This seems to be a leveldb bug. Any remedy to this problem? |
👋 Hey! Thanks for this contribution. Apologies for the delay in responding! We've decided to rearchitect Storj, so that we can scale better. You can read more about this decision here. This means that we are entirely focused on v3 at the moment, in the storj/storj repository. Our white paper for v3 is coming very, very soon - follow along on the blog and in our Rocketchat. As this repository is part of the v2 network, we're no longer maintaining this repository. I am going to close this for now. If you have any questions, I encourage you to jump on Rocketchat and ask them there. Thanks! |
Package Versions
Replace the values below using the output from
storjshare --version
.Replace the values below using the output from
node --version
.Expected Behavior
Please describe the program's expected behavior.
Actual Behavior
Please describe the program's actual behavior. Please include any stack traces
or log output in the back ticks below.
google/leveldb#408
Steps to Reproduce
Please include the steps the reproduce the issue, numbered below. Include as
much detail as possible.
The text was updated successfully, but these errors were encountered: