Skip to content
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

seaweedfs filer panic after server crash and restart #1326

Closed
tianjipeng opened this issue May 22, 2020 · 1 comment
Closed

seaweedfs filer panic after server crash and restart #1326

tianjipeng opened this issue May 22, 2020 · 1 comment

Comments

@tianjipeng
Copy link

tianjipeng commented May 22, 2020

Sponsors SeaweedFS via Patreon https://www.patreon.com/seaweedfs
Report issues here. Ask questions here https://stackoverflow.com/questions/tagged/seaweedfs

Describe the bug
We use leveldb2 as filer storage, after server crash and restart, filer will always panic when start it.

System Setup

  • command line: weed filer
  • OS version: centos7.4
  • output of weed version: 1.61
  • content of filer.toml:
    [leveldb2] enabled = true dir = "/filer" # directory to store level db files

Expected behavior
filer run normally

Screenshots
If applicable, add screenshots to help explain your problem.
image-2020-05-15-14-59-27-444

Additional context
I find the root cause that return the wrong err in weed/filer2/leveldb2/leveldb2_store.go :
WX20200522-172759
Meanwhile, leveldb2 provide Recover function to repaire corruted data,so if dbErr is ErrCorrupted,we should call Recover function.

@chrislusf
Copy link
Collaborator

Thanks a lot for the debugging! Good to learn this Recover feature!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants