Weird "Check" Errors

So I just installed v0.12 and thought I’d give the new “prune” a test, but wanted to run “check --read-data” first. Here’s what I got:

create exclusive lock for repository
load indexes
check all packs
pack 3181a451: not referenced in any index
pack bd860d20: not referenced in any index
pack ba012418: not referenced in any index
pack 2a42e658: not referenced in any index
pack 66ff3572: not referenced in any index
pack e0b24740: not referenced in any index
pack 1956d11a: not referenced in any index
7 additional files were found in the repo, which likely contain duplicate data.
You can run `restic prune` to correct this.
check snapshots, trees and blobs
read all data%  478 / 479 snapshots
[48:45] 100.00%  479 / 479 snapshots
Load(<data/c6cf28e25d>, 0, 0) returned error, retrying after 720.254544ms <data/c6cf28e25d> does not exist
Load(<data/0810073084>, 0, 0) returned error, retrying after 582.280027ms: unexpected EOF
rclone: 2021/02/23 04:25:56 ERROR : data/08/08100730843ad8590744f5f730acfe27f2b484ecbf400f72ea19334a2c39983b: Didn't finish writing GET request (wrote 786432/4409157 bytes): unexpected EOF
rclone: 2021/02/23 22:41:25 ERROR : data/d5/d57f452763a8187646eef7a4d47a8a42f5950006f2ba1440ee50dddf1f1547b6: Didn't finish writing GET request (wrote 262144/4724040 bytes): unexpected EOF
Load(<data/d57f452763>, 0, 0) returned error, retrying after 468.857094ms: unexpected EOF
[47:12:10] 100.00%  262301 / 262301 packs
no errors were found

It seems as though no errors were found. Am I safe to assume these error messages were just Rclone having a hiccup, and that the retries were successful? I wish it would print a follow-up “success” message, so you know when it works, if that’s the case.

Just wanted to double-check before I pruned the repository. Don’t want another mess on my hands haha

When files are loaded from the storage backend and this fails, restic automatically tries to reload those. So it seems those reloads were successful

Also, the new prune implementation has many consistency checks to prevent data loss if called with a corrupted repository.

1 Like

Good to know! I’ll give prune a whirl now. :grin:

Okay wow. Another big thanks to the folks who came up with the new prune implementation in v0.12. I just ran what would normally take a day or two in a few minutes! :astonished: :clap: :clap: :clap:

1 Like