Michael Eischer
Michael Eischer
> There's already an option --one-file-system. Can this feature use that option, instead of introducing a new one? Or does it already have a meaning on Windows? `--one-file-system` currently has...
If someone is interested in taking over this PR, please just create a new PR, then I'll close this one.
(Force pushed to fix the linter warning)
Does setting `RESTIC_FEATURES=backend-error-redesign=false` let the issue disappear? How long does `restic find --pack 95f3a150d40ea4a3415b713409711aad6bc21395faa2cd653769a64d5205a4db` run with restic 0.16.5?
A proper fix will likely require tackling https://github.com/restic/restic/issues/2421 .
> Setting the features flag on v0.17.0 did not resolve the issue; I get the exact same errors. That error and symptoms can only be caused by the backend rework....
Setting `--stuck-request-timeout 1h` should work around the error. But yes, as https://github.com/restic/restic/issues/2421 isn't fixed so far, the error still occurs out of the box.
I see two problems with that: - not all command implement a dry-run mode. Now, if you specify the `--dry-run` option for a command that doesn't support it, this will...
> * Could a big warning as soon as the command starts be useful for this? `WARNING: Restic is running in dry run mode because RESTIC_DRY_RUN is set. No changes...
@rawtaz The Docker images on the docker hub just contain the latest rest-server binary but no updates to the underlying base image. We have a ghcr docker image build pipeline...