You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Borg 1.4.x has some rather verbose logging when rebuilding/synchronizing the cache. Currently these logs are logged at the INFO level (and they result in one line per archive). On repositories with a large archive count, they result in unecessary log flooding.
It seems more appropriate to log these specific lines at the DEBUG level instead of INFO.
The default logging level of borg is WARNING, so you won't see INFO output.
If you give -v or --info, you are explicitly requesting it to be more verbose.
So, whether these lines are INFO or DEBUG is a matter of preference and also might depend on whether you use it interactively, looking at it and waiting for it (wondering what it does right now) or in a cronjob, capturing the log output and looking at it later.
Looking at the flow (in cache.py), there are both INFO and DEBUG output statements and the rest of the logs seem approrpriate for the output (and level) they produce.
These specific lines are producing lines PER archive which (IMHO) belongs in the DEBUG level since they are going to be pretty verbose for larger repos. The INFO logs are very useful to give you the overall flow (and times) for the operation.
Even when running via cron, these end up being pretty noisy when considering the rest of the logs and don't really add much to justify being at the INFO level.
Please consider downgrading these specific lines to DEBUG level making the overall logging much more appropriate, useful and less noisy.
Activity
ThomasWaldmann commentedon May 25, 2026
The default logging level of borg is WARNING, so you won't see INFO output.
If you give
-vor--info, you are explicitly requesting it to be more verbose.So, whether these lines are INFO or DEBUG is a matter of preference and also might depend on whether you use it interactively, looking at it and waiting for it (wondering what it does right now) or in a cronjob, capturing the log output and looking at it later.
quietquark commentedon May 26, 2026
Looking at the flow (in cache.py), there are both INFO and DEBUG output statements and the rest of the logs seem approrpriate for the output (and level) they produce.
These specific lines are producing lines PER archive which (IMHO) belongs in the DEBUG level since they are going to be pretty verbose for larger repos. The INFO logs are very useful to give you the overall flow (and times) for the operation.
Even when running via cron, these end up being pretty noisy when considering the rest of the logs and don't really add much to justify being at the INFO level.
Please consider downgrading these specific lines to DEBUG level making the overall logging much more appropriate, useful and less noisy.
cache sync: log per-archive messages at debug level, fixes #9659
Merge pull request #10217 from ThomasWaldmann/cache-sync-log-level-9659
ThomasWaldmann commentedon Aug 27, 2026
Fixed by #10217.