Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

borg-create: non-existing top level paths should be explicitly logged #6708

Closed
azrdev opened this issue May 19, 2022 · 1 comment
Closed

Comments

@azrdev
Copy link
Contributor

azrdev commented May 19, 2022

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).

  • client 1.1.17
  • server 1.1.16

Operating system (distribution) and version.

  • client Fedora 35
  • server Debian 11

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)

me@client$ borg create --stats --verbose --show-rc --compression auto,zstd,9 \
        ssh://server/~/borg02::client.{utcnow} \
        /etc \
        /home/me/directory-does-not-exist

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

@ThomasWaldmann
Copy link
Member

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.

@ThomasWaldmann ThomasWaldmann removed this from the 2.0.0b6 milestone Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants