-
-
Notifications
You must be signed in to change notification settings - Fork 754
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 crashes if parent dir of recursion root can not be opened #6374
Comments
Please give the precise command that led to that traceback. |
Standard
And this computer don't have |
Thanks for reporting this issue, I could reproduce and fix it. Just a hint (unrelated to this bug): You use lzma,9 - that is super slow and likely wastes a lot of cpu cycles for nothing. See our docs about the maximum recommended lzma level and maybe even better: consider using zstd (much more modern and likely better/faster than lzma). |
Great news. About that lzma, you're absolutely right. This is just an old server and the backup script was configured long time ago. I use zstd on other boxes with borgbackup. |
create: skip with warning if opening the parent dir of recursion root fails, fixes #6374
create: skip with warning if opening the parent dir of recursion root fails, fixes #6374
Have you checked borgbackup docs, FAQ, and open Github issues?
Yes
Is this a BUG / ISSUE report or a QUESTION?
Bug?
System information. For client/server mode post info for both machines.
Your borg version (borg -V).
borg 1.2.0
Operating system (distribution) and version.
Linux xxxx 5.16.0-1-amd64 #1 SMP PREEMPT Debian 5.16.7-2 (2022-02-09) x86_64 GNU/Linux
Hardware / network configuration, and filesystems used.
ext4, nothing fancy
Describe the problem you're observing.
After upgrading to 1.2 borg crashes when it cannot find file from the configuration. In 1.1.x version it skipped it with warning.
Can you reproduce the problem? If so, describe how. If not, describe troubleshooting steps you took before opening the issue.
Add non exisiting file to backup script.
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: