Michael Eischer
Michael Eischer
Restic 0.17.0 will enforce that HTTP connections make progress and interrupts them after a few minutes if they are stuck, see https://github.com/restic/restic/pull/4792 . That IMHO should fix the underlying issue....
Restic will print a message to stderr when retrying a request. Retrying stuck requests will only be available starting from restic 0.17.0. The current (hardcoded) timeout for stuck requests is...
@Framsfex can you try whether restic 0.17.0 fixes the stuck requests for you? Tweaking the 5 minute timeout is tracked in https://github.com/restic/restic/issues/4970 .
> I have updated restic to 0.17.0, but I cannot find a timeout option. > Is the "5 minute timeout" hardcoded? Yes, as mentioned adding such a option is tracked...
Judging from a quick search the error code indicates that creating the snapshot would require more storage than VSS is allowed to use. If I remember correctly, that is a...
The let's close this issue for now. Feel free to reopen it if the problem shows up again.
Is there a reason why you use overlapping weekly and monthly policies? The `forget` command already has a lot of options, so I'm rather cautious with adding new ones. I'll...
> Ran restic check, which reported an unreferenced pack, followed by numerous unreferenced files. Please provide a few samples of those error messages if you still have them. `unreferenced packs`...
> Which, in turn, put the brakes on additional uploads, which means that anything trying to write to the mounted mega.nz drive will likely fail, and then... well, I think...
Is there anything left to do here?