`restic restore` speeds asymptotically dropping towards zero!

[durval]

@ifedorenko

Unfortunately, when I verified the restored files (using shasum) I detected that two of them had their contents corrupted

Can you try restoring the corrupted files again, both using restic 0.9.5 and the out-of-order branch? If corruption is reproducible, can you try restore with --verify parameter, which tells restic to read the files after restore and verify checksum? Thank you in advance.

OK, I just found and fixed the issue. I’m reporting this in a new thread, both to avoid this one going more OOT than it already has, and for the problem and solution to stand more prominently, please follow it there: [PSA] ATTENTION anyone not using a recent master (ie, > 0.9.5) version: restic will NOT detect changed files if mtime is reset by the application (eg: MS Excel and .xls/.xlsx files on macOS)

Cheers,
– Durval.