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
Corrupted blob #4677
Comments
running the same test with the latest master branch (8b08b52). Results in a very similar error:
I'd like to try some older version of restic, to see whether this is a regression, but was not able to build any v0.9.6 or v0.9.0 or v0.8.3:
I made it skip the go version check, but don't know whats wrong with |
Please try whether the compression levels "auto" or "off" for Also please run |
With compression level
Now the corruption can be triggered much faster:
|
As noticed in https://forum.restic.net/t/check-reports-errors-wrong-data-returned/7201/5 , this data corruption bug only affects restic 0.16.3. |
Output of
restic version
What backend/service did you use to store the repository?
I reproduced this three times on a repository on a directly connected external hard drive and twice on a repository accessed via the rest interface. Always on fresh repositories.
Problem description / Steps to reproduce
Do you have any idea what may have caused this?
I suspect a software bug since (on 5 tries) always exactly one damaged blob is found.
No messages from the system about bad disk sectors.
This is on an AMD Ryzen 5600 6 core/12 threads CPU, 16GB ram, 512GB nvme running OpenBSD 7.4.
To search for memory problems I ran 12 instances of memtester on a total of 3GB of memory 4 times, heating up the CPU up to 60⁰C. I ran memtest86+ thoroughly half a year ago on this same machine. No errors found.
Did restic help you today? Did it make you happy in any way?
I enjoyed reading the (good) documentation. I'm pretty happy to have found a well designed backup solution.
The text was updated successfully, but these errors were encountered: