Dry run on brand new setup fails #507
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#507
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
I'm trying to a dry run of my new borg repo.
After going trough the config.yaml and running
borg --init
i do a dry run. (init runs fine)borgmatic -n -v 2
Don't see any good indication of what is actually going wrong.
I'm very new to using both borg and borgmatic, so i might have missed something obvious, sorry if thats the case.
Any help is greatly appreciated.
Environment
borgmatic version: 1.5.23
borgmatic installation method: Docker (b3vis/borgmatic)
Borg version: 1.2.0
Python version: 3.9.7
Borgmatic config file: (sensitive info replaced with *)
Show full config
Thank you for filing this and providing the helpful log and configuration info! So here's what I think is going on:
borg compact --dry-run
--dry-run
is not supported for thecompact
sub-command." It's also possible that some of Borg's usage is getting truncated.So I think the fix here is for borgmatic to be smart enough to skip calling
borg compact
altogether when a dry run is requested. In the interim as a work-around, you can try invokingborgmatic create --dry-run
which will skip compacting.This has been fixed in borgmatic master. Thanks again for bringing it to my attention. This fix will be part of the next borgmatic release!
Released in borgmatic 1.5.24.