borgmatic --info not working #101
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#101
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?
Hi I'm having a problem with using the --info option. It just errors and says I haven't specified any repos or archives. However if I add a line to specify the archive or repo, it then complains about unrecognized arguments.
Sorry I don't know how to enter code with this editor. Here is a pastebin.
https://pastebin.com/DakY25zR
OS: Ubuntu 16.04.5
Borg: 1.0.11
Borgmatic: How can I checK? I downloaded with "sudo pip3 install --upgrade borgmatic"
Have you generated a borgmatic configuration with
generate-borgmatic-configuration
as per the README? Without a configuration file,borgmatic --info
won't know what repository to operate on.And you can check the borgmatic version with
pip3 show borgmatic
.pip3 show borgmatic says I'm running 1.2.7
Yes I have /etc/borgmatic/config.yaml as well as a couple in /etc/borgmatic.d/
Here is a pastebin of the config.yaml...
https://pastebin.com/r0cqDhPu
I store backups from my server in /mnt/backups/ as well, and have configuration files for each of my HDDs in the /etc/borgmatic.d/ directory.
It's been creating and checking repos just fine, but I tried --info to see how much space I was using so far and got that.
Got it. Thanks for the clarification. Borg version 1.0.11 is pretty old at this point. Have you tried upgrading? I can try to reproduce this later on, but it may be worth trying Borg 1.1.7 or thereabouts, if possible, to see if that fixes this. They may have changed their
--info
sub-command semantics.Yep that fixes it, should have realized that version was too old.
Glad to hear that upgrading Borg cleared that up. For what it's worth, I've just set up a few more end-to-end tests in continuous integration to catch this sort of issue in the future. I've also mentioned a minimum Borg version in the README. Thanks for reporting the issue!