Verbose 1 is giving too much detail (IMO) #137
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#137
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?
I've been using 'verbose 1' for a long time and like it's output. But after updating borgmatic on a few systems, I've noticed they are giving a lot more output. It seems 'verbose 1' now gives output for every file it touches.
While this is fine for those wanting more detail, I feel that verbosity level 1 shouldn't. Level 0 gives almost no useful output other than "Start" and "Stop" and any errors. Which is also fine for that level. What I want is a little more than level 0, which is what we used to get, a nice summary of size, dedupe, compression, how much was gained or removed for pruning vs new backups.
But now the daily emails are thousands of lines long and we have to scroll a lot to get to the useful summary info.
Is this an oversight or bug or just a new way of doing verbose? If this is a new way, I'd like to request something like a Level 0.5, something in between nothing and way too much.
I've seen this on at least 5 systems that we've recently updated borgmatic on.
Assuming that the list of files you're seeing is only the list of changed files, this is an intentional change rather than a bug. This new way of doing verbosity happened in borgmatic 1.2.3. From the changelog:
Please feel free to check out any of those tickets for more details.
However, in borgmatic 1.2.13, a
--stats
option was added:So with recent versions of borgmatic, you can try
--verbosity 0
in combination with--stats
to see if that's closer to the old behavior you're looking for. In any case, please let me know!Ok, sounds possible...
So I removed '-v 1' and added '--stats'. Now I get errors.
Traceback (most recent call last):
File "/usr/local/bin/borgmatic", line 11, in
sys.exit(main())
File "/usr/local/lib/python3.6/dist-packages/borgmatic/commands/borgmatic.py", line 355, in main
args = parse_arguments(*sys.argv[1:])
File "/usr/local/lib/python3.6/dist-packages/borgmatic/commands/borgmatic.py", line 170, in parse_arguments
raise ValueError('The --stats option can only be used with the --create or --prune options')
ValueError: The --stats option can only be used with the --create or --prune options
What I've been doing is just running borgmatic with no options except '-v 1'. So that it would run through all 3, prune, create, check.
I guess now I'm going to have to figure out yet another script wrapper to run all of them one at a time. Less than ideal.
Well that's silly! 😄 Why don't I make the argument parsing exception you mention above more surgical, so that it allows
borgmatic --stats
even without specifying particular--create
or--prune
flags?Filed #138 to better handle that situation.
Okay, I implemented #138 and it'll go out as part of the next release. (Likely today.) But let me know if you find any other rough edges.
Just released in borgmatic 1.2.15.
Just updated and tried it. Yup, that looks much better! Thanks for helping out!
Cool, glad to hear it! If you have any other problems or ideas for improvements, please feel free to file a ticket.