-
Hello, I'm not sure if this is a bug so before opening an issue, I would like to ask here. All of a sudden I'm getting lots off error messages when running borgbackup on my external USB-HDD, also when pruning. The error messages for "borg create" look like this:
It is always the .../3/3875 but different local files. then this messages appear:
When I ran
Unfortunately I have no idea what I could try to solve the problem. Any help would be apreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 5 replies
-
Why is that showing up in between borg output? borg is not using Qt nor translations. It looks like that repo is corrupted in a strange way that borg check --repair can't fix. Can you do:
|
Beta Was this translation helpful? Give feedback.
-
Thank you for taking a look. The "kf.i18n"-Warning is probably unrelated. I think it comes because I get the passphrase from the KDE-Wallet like this
Here is the output of "ls -l /media/xyz/BACKUP1500GB/Backup/xyz"
and last lines of "ls -lR /media/xyz/BACKUP1500GB/Backup/xyz/data"
|
Beta Was this translation helpful? Give feedback.
-
What you could try: just retryConsidering that the file it complained about being in the way is gone, just retry:
alternatively, kill all indexes/caches and repair
|
Beta Was this translation helpful? Give feedback.
-
BTW, you seem to have many 17b files from borg 1.1. After you repaired the repo, do this step from the changelog / upgrade notes once per repo for all repos that used borg < 1.2 before:
|
Beta Was this translation helpful? Give feedback.
-
OK. Orphaned/superseeded is no big issue, just stuff that is not referenced by an archive. But in another check run it complained about a missing chunk and that it replaced it by an all-zero replacement chunk. But maybe proceed as follows:
|
Beta Was this translation helpful? Give feedback.
Ok, i think I fixed it. I thought: The OS sees that "3875" exists even though it doesn't seem to exist. Maybe it is a file-system problem? The disk is NTFS-format so I tried "ntfsfix". It found problems but is unable to fix it. So I had to start a Windows-machine to run proper "chkdsk". This seemed to do the trick. Now borg check ran fine and found a lot of problems in the latest archive.