aawsome
aawsome
@dimitarvp: Please have a look if this is what you are requesting and feel free to add missing points!
@dimitarvp Sorry, I didn't get it - and I am somehow confused. First, if you run your second command `cd $HOME && rustic backup .config .vimrc`, you get an output...
I had a small look into the code to check how easy it is to implement this feature. I must say that I would like to combine this with a...
Thanks a lot @9-2-1 for opening this issue! I tried to reproduce using ``` rustic backup --init rustic backup --init rustic backup --init rustic copy --init ``` and I am...
Ok, I think I found the reason: - The copying is parallelized - we check existence of a blob in (the repository / the already written packs / the in-flight...
#148 does not fully solve the issue but makes it much more unlikely. To fully solve it we need to do a big refactor of how packaging of blobs works...
@9-2-1 Can you check if your problem still exist using the latest nightly builds?
I tried to dig a bit into this topic. Indeed it seems that the only way to detect hard links within a filesystem is to check the number of links...
Agree to @simonsan - when the backend refactor is done, the TLS things will be all in the crate rustic_backends, so we better wait for the refactoring #73 to land!...
Now that #73 is merged, this PR can continue... @jirutka: Your changes should now go to `crates/backend`. Can you move this or do you need support? Also, now that we...