How to find corrupted files reported by `check`?

Support
#1 
$ duplicacy check -files -id test -r 1 -persist
Storage set to /home/dup/duplicacy
Listing all chunks
1 snapshots and 1 revisions
Total chunk size is 703,685M in 146295 chunks
Chunk 492ee84cd5e7e37c4f19a32d3eb71cf80a3219660d3a52777022038882497bb5 can't be found
Snapshot test at revision 1 contains 1 corrupted files

But I’d like to know which file is corrupted.

BTW does -chunk coupled with -persist flag mean that after the completion of this check, only one missing chunk and one corrupted file is found, and everything else if fine?

#2

Create a repository in a different folder and then run a restore. This should tell you which file is corrupted:

cd \another\folder
duplicacy init test /home/dup/duplicacy
duplicacy restore -r 1
#3

Well there are two problems… first is that I’m running the check on the storage target where I don’t have enough free disk space to do a restore; and second is that restore across the network would be incredibly slow given the ~700GB size…

I’m wondering why cannot check just print the path of the corrupted files? It surely knows which files are corrupted right?

1 Like
#4

It would actually be good if the “check” could give the names of the files concerned on the errors.

1 Like