aawsome
aawsome
If you want to remove all snapshots, it is easier to remove the repo and re-create it. In general, removing snapshots only frees space if you run a `prune` afterwards.
Yes, `prune` does a two-phase pruning by default which allows parallel operations on a repository. Therefore all data is just marked for removal. Either you wait 23h and re-run, or...
This error comes when the paths can't be sanitized because they (some?) don't exist. Can you please run `rustic backup --log-level debug` by manually giving the paths? I think the...
Ok, I tried to reproduce the issue and can confirm that an empty dir (as part of the source) is simply not backuped. There might be some exceptions when using...
@MichaelEischer Note that padding can be easily added to the pack file specification. I added the PR #5331 which describes it. I don't remember exactly how the implementation is but...
> I'll retry using an uncompressed blob of zeros as padding. Agree, I think this is the easiest way. Older versions will then just see an unused blob; newer versions...
You could do it vice versa and use the value from the configuration instead of the one given by the commandline in your code. Then, use `override_config` to set/override the...
Thanks for opening this issue @ociaw In fact, yes rustic should retry here as this is classified as a temporary error - and it is even saying it is retrying....
Hi @ociaw, in rustic 0.9.5 we improved error output - can you please retry if you see the same behavior and information using the newest version? Thanks a lot!
@ociaw The idea about the SIGPIPE handler is to get correct error codes for failing pipe situations. We especially had in mind a `command | rustic backup -` where command...