Hi there. I have read through Fix missing chunks but I don’t seem to figure out what had happened.
The prune operation run after scheduled backup via UI 2.1.1 on MacOS started reporting this:
15:08:29.705 Chunk 737dcbc402cbf1b455c963c504738c00405f120c8ec1807f91289bdd3d1bfa89 does not exist in the storage
Searching through the logs for that chunk ID I only see this:
myhmbp:logs me$ g 737dcbc402cbf1b455c963c504738c00405f120c8ec1807f91289bdd3d1bfa89 ./backup-log-20180801-150513:102:2018-08-01 15:08:29.705 ERROR CHUNK_FIND Chunk 737dcbc402cbf1b455c963c504738c00405f120c8ec1807f91289bdd3d1bfa89 does not exist in the storage ./backup-log-20180801-150513:104:ERROR Chunk 737dcbc402cbf1b455c963c504738c00405f120c8ec1807f91289bdd3d1bfa89 does not exist in the storage ./prune-log-20180730-212848:14:Marked fossil 737dcbc402cbf1b455c963c504738c00405f120c8ec1807f91289bdd3d1bfa89 ./prune-log-20180730-230324:15:Deleted fossil 737dcbc402cbf1b455c963c504738c00405f120c8ec1807f91289bdd3d1bfa89 (collection 1) ./prune-log-20180731-220344:2:Marked fossil 737dcbc402cbf1b455c963c504738c00405f120c8ec1807f91289bdd3d1bfa89 ./prune-log-20180801-150823:5:Marked fossil 737dcbc402cbf1b455c963c504738c00405f120c8ec1807f91289bdd3d1bfa89 ./backup-log-20180730-230000:108:2018-07-30 23:03:29.559 INFO CHUNK_DELETE The chunk 737dcbc402cbf1b455c963c504738c00405f120c8ec1807f91289bdd3d1bfa89 has been permanently removed
I did invoke prune with -exhaustive flag once (seemingly around the time the issue started as far as I remember), but never with -exclusive; and the logs above seem to imply that the chunk was not deleted during prune, but during backup.
duplicacy -background check -a -fossils results in everything being OK with all revisions except one, that is missing a lot of chunks
What could have happened?
What additional logging can I provide to help triage this?