Object with key ... not found in repository #600
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#600
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'm trying to do and why
Create local backup. Remote backup seems to work fine (in the same config file).
Steps to reproduce (if a bug)
docker exec Borgmatic sh -c "cd && borgmatic --stats -v 1 --files 2>&1"
Actual behavior (if a bug)
Environment
docker 20.10.18
borgmatic 1.7.4
borg 1.2.2
apprise 1.1.0
Python 3.10.8
Applying custom cron
Cron job set as:
0 5 * * * borgmatic --stats -v 0 2>&1
Not quite sure what "Object with key d300371ef50b97ee32356e93a6a5fe7c9e7a7a603a41856ac12a7e7b39f67e35 not found in repository /mnt/borg-repository." is, but as far as I know, the repo data should be good.
If it's beyond saving, it's not a big issue, I'll just recreate it, but it'd be good to understand the why/what and maybe potentially think of a more suitable error message for users (working on the assumption of zero knowledge by said user).
Interesting.. This looks like another Borg repository consistency issue. Have you tried
check --repair
? Have there been any hardware failures or other problems with this repository that might explain this occurring?Also, the response in this ticket may be helpful: https://github.com/borgbackup/borg/issues/2414
Heya,
The message comes up immediately, even if I run:
docker exec Borgmatic sh -c "cd && borgmatic check --only data --only extract --verbosity 1 --monitoring-verbosity 1"
Or
borgmatic check --progress --repair
It's almost as if it's unable to find one of the files that define the repo as stated in the other ticket.
Zero hardware issues, ram is ECC (with nothing on memtest), and hdd's are all showing good with smart.
Certainly an unusual one!
I'll give "borg delete --cache-only repo" a bit later and see what happens!
Worst case, I'll recreate the repo as it's quite an old one, so it might be a good shout.
Thanks!
I recreated the repo, and no issues so far.
Looks like it may have just been a weird issue, but I'll keep an eye.
Thanks!
Glad to hear it's at least working for now!