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

"LevelDBError: Corruption: CURRENT file does not end with newline" database recovery was not possible #75

Closed
cmumford opened this issue Sep 9, 2014 · 2 comments
Assignees

Comments

@cmumford
Copy link
Contributor

cmumford commented Sep 9, 2014

Original issue 69 created by vera.voropaeva@phystech.edu on 2012-01-26T14:04:40.000Z:

What steps will reproduce the problem?

  1. we tested synchronous and async write operations
  2. while writing a big block of data we turned of the PC
  3. on the next computer start: LevelDBError: Corruption: CURRENT file does not end with newline

Database recovery did not start automatically.
We were unable to recover the database

@cmumford
Copy link
Contributor Author

cmumford commented Sep 9, 2014

Comment #1 originally posted by sanjay@google.com on 2012-01-26T16:44:57.000Z:

Yesterday's release (git commit 3c8be10) should have fixed this.

@cmumford cmumford self-assigned this Sep 9, 2014
@cmumford cmumford closed this as completed Sep 9, 2014
@ne0ark
Copy link

ne0ark commented Mar 18, 2017

I am getting this also. {"level":"error","message":"Could not get usedSpace: Corruption: CURRENT file does not end with newline","timestamp":"2017-03-17T12:29:29.015Z"} when using mounted google drive using fuse and https://github.com/Storj/kfs

maochongxin pushed a commit to maochongxin/leveldb that referenced this issue Jul 21, 2022
Add _build to gitignore to enable out-of-source builds
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