TW
one could do a new test using pyfuse3 after #4122 is closed.
So, did you use borg encryption for that repo? If so, do you still have (a backup of) the key? The unhexlify traceback means that the repo id in the...
The id is not an arbitrary string, but it must be exactly 64 hex digits. Have a look at a valid config file you can get by just running `borg...
And you're lucky you did not use repokey encryption - if you lose the config with the encryption key, you can not recover anything inside this repo (that's the reason...
Missing file chunks means that your repo/data/ directory copy was corrupted. Not sure what you mean with your last sentence.
The distribution of archive chunks over segment files is not strictly linear, it is not as simple as you think it is. What you should do is start from a...
Can you please read our docs about the terms "archive", "segment files" and "repository"? You seem to use these terms differently and that's quite confusing.
@fantasya-pbem did you have a look at this already?
IIRC, when borg is doing the recursion and feeding names into the matcher, a directory name looks like `path/to/directory` and files on the same level look like `path/to/file` (note that...
maybe it currently can only cope with the (unlikely?) case that your key got removed from the config somehow. the other repo params are easy to reconstruct by looking at...