Closed mathiasslawik closed 7 years ago
That looks like a corrupted "files" cache. Maybe check if the cache was really removed (permissions?).
The borg delete --cache-only repo
code should have killed the whole cache directory (in a rm -rf
way), so it is strange that there seems to be an invalid files
cache file left.
The cache is in $HOME/.cache/borg/<repoid>/
assuming you did not point it somewhere else via env vars.
As a side note: borg 1.1 will protect important files by checksums/hashes, so any corrupt file will be recognized.
Maybe we could have a simple fix for 1.0, just starting a new files cache from scratch in case of unpack errors.
@mathiasslawik see #2941 - I tested it by manually corrupting the files cache (got the same TypeError as you) and it can deal with it now.
Hello,
unfortunately, I had a "corrupted chunks index" due to filesystem corruption (that I myself caused - but that's another story). To fix it, I invoked
borg delete --cache-only
that removed the local cache. However, I now get the following error when trying to run the backup:I really don't know if it's a very stupid simple error that I'm causing or if there is something else going on here. As a background: I'm doing a backup of my root partition to a directory on a large RAID5 array which I later sync to another server. Until the corruption happened, the backup ran without a problem for at least half a year. You see two machines ("darkroom" and "switchy") as I backup also a portable device to the same repo to use deduplication as both use Archlinux. I run borg through borgmatic as a systemd timer job.
If there's anything else you need, please let me know. Thanks in advance for looking into this issue.
Best regards, Mathias