-
-
Notifications
You must be signed in to change notification settings - Fork 743
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
[1.2.0a6] KeyError and AssertionError on first backup, subsequent backups do not have errors #4577
Comments
Having that kind of locking problems on a freshly initialized repo seems strange. |
Both the computer and backup drive are using BTRFS. |
Can you use a device formatted with ext4 and try to reproduce? |
I just tried it on a few different file systems, ext4 included, seems that the error is the same. It seems to be backing up a windows .img file when it fails. |
OK, just wanted to make sure we do not debug btrfs issues here. I'll try to reproduce the issue locally. |
Can you try to reduce the borg commands to a minimum (regarding options, excludes, etc), so you can post the minimum of commands needed that still reproduces the issue? What exactly is a "windows .img" file? A picture? A (virtual machine) disk image? Something else? |
When reducing the commands to a minimum which reproduces the error I came up with: Produces error: Does not produce error: Other findings:
|
I did a couple more tests. In the first I ran it with lzma,9. The second, default. The first generated the errors and the second did not. The drive was formatted with xfs in the first and fat32 in the second.
|
It doesn't affect your minimalistic reproductions, but some comments about your original command:
|
Also, I'ld appreciate if you use minimalistic commands in further research. It doesn't help if there are a ton of options / arguments if they are not needed to reproduce the problem. Preferably also do not use wildcards, shell variables and sudo, it just complicates matters and we are searching bugs in borg here, not in scripts. |
I read The locking system relies on unique keys and it makes them from fqdn and MAC address. Do you have other hosts with same |
Thank you for your suggestions. I will make sure to follow them. Yeah that is my fqdn, this is the only computer using borg at the moment, no other computers with the same MAC. |
Any news? If you can give a minimal script, that reproduces the problem on your machine (and also hopefully on mine), that would help a lot. |
No feedback... |
Have you checked borgbackup docs, FAQ, and open Github issues?
Yes
Is this a BUG / ISSUE report or a QUESTION?
BUG / ISSUE report and QUESTION
System information. For client/server mode post info for both machines.
Your borg version (borg -V).
1.2.0a6
Operating system (distribution) and version.
NAME="Manjaro Linux"
Release: 18.0.4
Kernel: Linux 5.1.0-1-MANJARO
Architecture: x86-64
Hardware / network configuration, and filesystems used.
How much data is handled by borg?
80GB
Full borg commandline that lead to the problem (leave away excludes and passwords)
borg create -v --stats --progress --compression zstd,22 --chunker-params 10,23,16,4095 $REPO::$HOST-$DATE /
--exclude /dev
--exclude /proc
--exclude /sys
--exclude /var/run
--exclude /run
--exclude /tmp
--exclude /lost+found
--exclude /mnt
--exclude /var/cache
--exclude /home/*/.cache
--exclude /home/ds/Downloads
--exclude /home/lost+found
Describe the problem you're observing.
On the first run of borg create after init, I get an error after about 4GB of deduplicated data. Following backups do not throw any errors.
Can you reproduce the problem? If so, describe how. If not, describe troubleshooting steps you took before opening the issue.
Yes it is reproducible on my system. Happens every time on first backup after init.
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: