#2880 Issue closed: Borg wil not work anymore after updating to rear 2.7-1 (github)¶
Labels: waiting for info, no-issue-activity
roseswe opened issue at 2022-10-12 12:36:¶
1.) make rpm -> rear-2.7-1.git.4914.dbc0c6f9.master.x86_64.rpm
2.) zypper in ./rear-2.7-1.git.4914.dbc0c6f9.master.x86_64.rpm
3.) rear -D -v mkbackup
:::
#++ borg list /dev/disk/by-label/REAR-000//borg_rear
Local Exception
Traceback (most recent call last):
File "borg/archiver.py", line 4703, in main
File "borg/archiver.py", line 4635, in run
File "borg/archiver.py", line 162, in wrapper
File "borg/repository.py", line 190, in __enter__
File "borg/repository.py", line 415, in open
NotADirectoryError: [Errno 20] Not a directory: '/dev/disk/by-label/REAR-000/borg_rear'
Platform: Linux p5520 5.3.18-150300.59.93-preempt #1 SMP PREEMPT Tue Sep 6 05:05:37 UTC 2022 (7acce37) x86_64
Linux:
Borg: 1.1.17 Python: CPython 3.7.11 msgpack: 0.5.6.+borg1
PID: 8587 CWD: /etc/rear
sys.argv: ['borg', 'list', '/dev/disk/by-label/REAR-000//borg_rear']
SSH_ORIGINAL_COMMAND: None
+ source_return_code=2
4.) fallback: rear23a-2.3.a-19.9.x86_64.rpm
5.) # rear -v mkbackup
Relax-and-Recover 2.4 / Git
:::
jsmeix commented at 2022-10-13 13:41:¶
I am not a Borg backup user so I cannot actually help
with Borg backup specific issues.
In general regarding issues with third-party backup tools:
Usually we at ReaR upstream do not use third-party backup tools
so usually we cannot reproduce issues with third-party backup tools.
Nevertheless we try to help as good as we can from plain looking at the
code.
But to do that we need to know what ReaR scripts are actually run
and what actually happens while those ReaR scripts are run.
This is why we ask for specific information
when submitting a ReaR upstream issue, see
https://github.com/rear/rear/blob/master/.github/ISSUE_TEMPLATE.md
therein note in particular the last part about
"rear -D mkrescue/mkbackup/recover" debug log files
Furthermore see the section
"Debugging issues with Relax-and-Recover" in
https://en.opensuse.org/SDB:Disaster_Recovery
github-actions commented at 2022-12-17 02:21:¶
Stale issue message
[Export of Github issue for rear/rear.]