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
When passing a PATH to borg create that does not exist (among others that do), it returns 1 indicating "warning (operation reached its normal end, but there were warnings -- you should check the log, logged as WARNING)" but there is nothing logged to stdout/err, even with --verbose. In other words: borg states something failed, and I should see why above, but I don't.
Adding --list --filter='E?' reveals that the top-level PATH was not found (in my case a typo, which excluded the meant directory from backups).
In such a case, I'd expect the missing top-level PATH to be printed (at least on --verbose).
Can you reproduce the problem? Yes
Include any warning/errors/backtraces from the system logs
none
The text was updated successfully, but these errors were encountered:
I just tried to reproduce with borg 1.2-maint branch:
(borg-env) tw@mba2020 borg % borg create repo12::archive src/ foobar/ docs/
Enter passphrase for key /Users/tw/w/borg/repo12:
foobar: [Errno 2] No such file or directory: 'foobar'
So I guess this was either fixed at some time or you just overlooked the output.
Have you checked borgbackup docs, FAQ, and open Github issues?
Yes
Is this a BUG / ISSUE report or a QUESTION?
ISSUE
System information. For client/server mode post info for both machines.
Your borg version (borg -V).
Operating system (distribution) and version.
Hardware / network configuration, and filesystems used.
irrelevant, I think
How much data is handled by borg?
irrelevant, I think
Full borg commandline that lead to the problem (leave away excludes and passwords)
Describe the problem you're observing.
When passing a PATH to
borg create
that does not exist (among others that do), it returns 1 indicating "warning (operation reached its normal end, but there were warnings -- you should check the log, logged as WARNING)" but there is nothing logged to stdout/err, even with--verbose
. In other words: borg states something failed, and I should see why above, but I don't.Adding
--list --filter='E?'
reveals that the top-level PATH was not found (in my case a typo, which excluded the meant directory from backups).In such a case, I'd expect the missing top-level PATH to be printed (at least on --verbose).
Can you reproduce the problem? Yes
Include any warning/errors/backtraces from the system logs
none
The text was updated successfully, but these errors were encountered: