Understanding output from check --read-data after resume from suspend

I ran restic-check --read-data in my notebook and as expected it took several hours to complete. In the middle of the process, I had to commute home-office-home, putting it to suspend a couple of times. Restic/Rclone were able to resume the process as long as the machine woke up and got wifi signal. The process ended with exit code = 0 and no errors were found. BUT I got several scary messages in the middle, which I would like to confirm have nothing to do with the integrity of my backups. So I came here for help.

Below follows the exact restic command:

restic -r rclone:ufop:restic check --read-data >> /home/oliveira/.backup-logs/restic-dell.log 2>&1

And the logs:


using temporary cache in /tmp/restic-check-cache-3969906558
create exclusive lock for repository
load indexes
check all packs
check snapshots, trees and blobs
[0:40] 100.00%  20 / 20 snapshots

read all data
Load(<data/4e53e173a9>, 0, 0) returned error, retrying after 720.254544ms: <data/4e53e173a9> does not exist
Load(<data/f485df987d>, 0, 0) returned error, retrying after 582.280027ms: <data/f485df987d> does not exist
Load(<data/3406c28404>, 0, 0) returned error, retrying after 468.857094ms: <data/3406c28404> does not exist
Load(<data/48fded010b>, 0, 0) returned error, retrying after 462.318748ms: <data/48fded010b> does not exist
rclone: 2022/08/18 08:04:15 ERROR : data/f6/f63f61c61ac334d574e9286d172eb6e30bbedb53a03e63319f2e23b0274fb2e0: Didn't finish writing GET request (wrote 80726/7334431 bytes): read tcp 192.168.2.13:46398->142.251.134.106:443: read: connection reset by peer
rclone: 2022/08/18 08:04:15 ERROR : data/2c/2c6e0d0373c2d061eb8391fbe1dc53270b7c1c878904ed9411fe5625f916b893: Didn't finish writing GET request (wrote 47973/7381869 bytes): read tcp 192.168.2.13:35242->142.250.218.42:443: read: connection reset by peer
Load(<data/f63f61c61a>, 0, 0) returned error, retrying after 593.411537ms: unexpected EOF
Load(<data/2c6e0d0373>, 0, 0) returned error, retrying after 282.818509ms: unexpected EOF
Load(<data/c7aefbc349>, 0, 0) returned error, retrying after 328.259627ms: <data/c7aefbc349> does not exist
Load(<data/aac5e70aad>, 0, 0) returned error, retrying after 298.484759ms: <data/aac5e70aad> does not exist
rclone: 2022/08/18 10:28:30 ERROR : data/ef/efd4e4c436531bac25b1ad9b8d20561102275aacb975513e84d6b5984298e686: Didn't finish writing GET request (wrote 80724/4619894 bytes): read tcp 192.168.2.9:56232->142.250.218.138:443: i/o timeout
Load(<data/efd4e4c436>, 0, 0) returned error, retrying after 400.45593ms: unexpected EOF
[9:59:44] 100.00%  56088 / 56088 packs

no errors were found
Exit Code: 0

What backend are you using? I mean, on the rclone side - what storage system?

Ho, sorry. Forgot to mention that. I’m using Google Drive with my own credentials (not rclone’s one. Not sure if this information is important).

Was just curious. I personally would not be worried by the output, it’s all just a bunch of retries reported and if it couldn’t be read in the end restic would not tell you everything is good.

Yeah… I presumed Restic would not exited 0 if something went wrong. Thanks for your input.