How to deal with missing data files

1

I am doing a restic check --read-data and there is some cases of missing data files — see below.

There is only 1 snapshot and so all source files still around —

Is there anyway have restic force recreate the missing files?

read all data
Load(<data/8ec528bfcb>, 0, 0) returned error, retrying after 720.254544ms: <data/8ec528bfcb> does not exist
Load(<data/8ec528bfcb>, 0, 0) returned error, retrying after 873.42004ms: <data/8ec528bfcb> does not exist
Load(<data/8ec528bfcb>, 0, 0) returned error, retrying after 1.054928461s: <data/8ec528bfcb> does not exist
Load(<data/8ec528bfcb>, 0, 0) returned error, retrying after 1.560325776s: <data/8ec528bfcb> does not exist
Load(<data/8ec528bfcb>, 0, 0) returned error, retrying after 3.004145903s: <data/8ec528bfcb> does not exist
Load(<data/8ec528bfcb>, 0, 0) returned error, retrying after 2.147653057s: <data/8ec528bfcb> does not exist
Load(<data/8ec528bfcb>, 0, 0) returned error, retrying after 3.739082318s: <data/8ec528bfcb> does not exist
Load(<data/8ec528bfcb>, 0, 0) returned error, retrying after 5.099891944s: <data/8ec528bfcb> does not exist
Load(<data/8ec528bfcb>, 0, 0) returned error, retrying after 10.263247495s: <data/8ec528bfcb> does not exist
Load(<data/8ec528bfcb>, 0, 0) returned error, retrying after 19.514091959s: <data/8ec528bfcb> does not exist
checkPack: Load: <data/8ec528bfcb> does not exist
rclone: 2022/07/03 13:09:40 ERROR : data/df/df15bb3df8c2f90c9fba03f265f423de0942fe4c4b3b9df123a335ca5e718ef4: Didn't finish writing GET request (wrote 2621440/6958032 bytes): unexpected EOF
Load(<data/df15bb3df8>, 0, 0) returned error, retrying after 656.819981ms: unexpected EOF
rclone: 2022/07/03 13:09:49 ERROR : data/84/84ecf99534a5ba55ce6e231655c76a9e97310c498249307f097bbc405c6dfcf0: Didn't finish writing GET request (wrote 524288/5614227 bytes): unexpected EOF
Load(<data/84ecf99534>, 0, 0) returned error, retrying after 357.131936ms: unexpected EOF
Load(<data/e475bf0687>, 0, 0) returned error, retrying after 440.328595ms: <data/e475bf0687> does not exist
Load(<data/e475bf0687>, 0, 0) returned error, retrying after 613.543631ms: <data/e475bf0687> does not exist
Load(<data/e475bf0687>, 0, 0) returned error, retrying after 1.090001075s: <data/e475bf0687> does not exist
Load(<data/e83f9373dc>, 0, 0) returned error, retrying after 391.517075ms: <data/e83f9373dc> does not exist
Load(<data/e83f9373dc>, 0, 0) returned error, retrying after 594.826393ms: <data/e83f9373dc> does not exist
Load(<data/e83f9373dc>, 0, 0) returned error, retrying after 1.326470261s: <data/e83f9373dc> does not exist
Load(<data/e83f9373dc>, 0, 0) returned error, retrying after 1.212558276s: <data/e83f9373dc> does not exist
Load(<data/e83f9373dc>, 0, 0) returned error, retrying after 1.779941781s: <data/e83f9373dc> does not exist
Load(<data/e83f9373dc>, 0, 0) returned error, retrying after 3.268621161s: <data/e83f9373dc> does not exist
Load(<data/e83f9373dc>, 0, 0) returned error, retrying after 6.097818893s: <data/e83f9373dc> does not exist
Load(<data/e83f9373dc>, 0, 0) returned error, retrying after 11.639721773s: <data/e83f9373dc> does not exist
Load(<data/e83f9373dc>, 0, 0) returned error, retrying after 10.163325309s: <data/e83f9373dc> does not exist
Load(<data/e83f9373dc>, 0, 0) returned error, retrying after 15.321265721s: <data/e83f9373dc> does not exist
checkPack: Load: <data/e83f9373dc> does not exist
2

You could try route 2 from Recover from broken pack file · Issue #828 · restic/restic · GitHub , that is rename/remove the inaccessible files, then run rebuild-index and afterwards run backup again.

But first it would be a good idea to find out why the storage backend (where is the data stored?) claims that a files exists, but the fails to retrieve it. Restic is so far not built to gracefully handle a backend that just looses data.