-
Notifications
You must be signed in to change notification settings - Fork 70
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
Unrepairable repository corruption when using flaky FUSE drive as repository #1164
Comments
After switching from GVFS to It's also weird that
And at other times this makes
When I re-build with debug profile, it fails with a different error quite early:
|
This is a whole saga and not Rustic's fault.
All of this has been with stable Rustic version v0.7.0
I tried using GNOME's OneDrive integration (gvfs-daemon via FUSE) as my backup repository. Due to memory leaks,
gvfsd-onedrive
kept crashing (killed by OOM killer), resulting in Rustic reporting an I/O error in the middle of the backup. I retried lot of times and tried to cancel the backup manually before the system ran out of memory, and eventually completed the backup this way. (Some irrelevant details here: #1161 (comment))But the resulting repository has some unfixable corruption. I would be even more impressed with
rustic
if were able to fix this mess. 😆rustic check
is now reporting lots of issues. I ran bothrustic repair index
andrustic repair snapshots
a few times. They seemed to complete successfully, but this has not solved the corruption.During index check there are warnings like:
And later from checking trees I get errors:
I later switched from GVFS to using
rclone
to access OneDrive. With rclone, on the same repo, I'm seeing following errors and also panics, see comment below.Full output from `rustic check`
The text was updated successfully, but these errors were encountered: