TW
Ah, ok, that made it clearer. I have a slightly hackish solution that has the advantage of not needing a change in borg: ``` put `` in backup mode ts...
@Daniel-Nashed sounds like a plan. And your code then can notice when tar finishes, then also borg is done with that file and you can continue to the next one).
Yes, you can apply this to existing repos, but it won't change the size of already existing segment files. But: if such a segment file would get compacted (because of...
Using 50 or 100MB segment size is perfectly reasonable, esp. for remote repos or repos that get rsynced to somewhere.
You can also carefully edit repo/config, it is a text file.
Yeah, it's a bit complicated. The main problem there is permissions: - there are some settings in the config that the repo hoster might not want to let the repo...
Theoretically yes. But for that working with remote repos, the repo server side borg would also need to support that.
``` borg.helpers.errors.IntegrityError: Data integrity error: Invalid segment entry header [segment 37, offset 27231398]: unpack requires a buffer of 41 bytes ``` Looks like the segment file 37 in that repo...
You can ignore / delete the `*.tmp` files. But the file `37` looks like it has some content, maybe try to read it / look inside . Also, a `fsck`...
``` FileNotFoundError: [Errno 2] No such file or directory: '/mnt/borgbackup/borg/data/0/37-hseny2eo.tmp' ``` Interesting that you have that file in your `ls` output.