I have scheduled check followed by prune on B2.
Check complained about missing chunks, which prune subsequently tried to fossilize but that chunk was apparently already a fossil. There is no other mention of that chunk anywhere. What could have happened?
alex@Tuchka:/var/services/homes/duplicacy-web/.duplicacy-web/logs$ grep -C 2 -R "cba6d3dbb864ec31270dcfb57025ec426dc414877c2fdcc7890410b43b5bbeae" . ./check-20200506-033001.log-2020-05-06 03:32:51.778 INFO SNAPSHOT_CHECK All chunks referenced by snapshot tuchka at revision 747 exist ./check-20200506-033001.log-2020-05-06 03:32:53.783 INFO SNAPSHOT_CHECK All chunks referenced by snapshot tuchka at revision 774 exist ./check-20200506-033001.log:2020-05-06 03:32:57.397 WARN SNAPSHOT_VALIDATE Chunk cba6d3dbb864ec31270dcfb57025ec426dc414877c2fdcc7890410b43b5bbeae referenced by snapshot tuchka at revision 776 does not exist ./check-20200506-033001.log-2020-05-06 03:32:57.620 WARN SNAPSHOT_CHECK Some chunks referenced by snapshot tuchka at revision 776 are missing ./check-20200506-033001.log-2020-05-06 03:32:59.570 INFO SNAPSHOT_CHECK All chunks referenced by snapshot tuchka at revision 798 exist -- ./prune-20200506-034655.log-2020-05-06 03:48:49.054 INFO SNAPSHOT_DELETE Deleting snapshot tuchka at revision 891 ./prune-20200506-034655.log-2020-05-06 03:48:50.480 INFO SNAPSHOT_DELETE Deleting snapshot tuchka at revision 892 ./prune-20200506-034655.log:2020-05-06 03:59:54.253 WARN CHUNK_FOSSILIZE Chunk cba6d3dbb864ec31270dcfb57025ec426dc414877c2fdcc7890410b43b5bbeae is already a fossil ./prune-20200506-034655.log-2020-05-06 04:00:14.924 INFO FOSSIL_COLLECT Fossil collection 13 saved ./prune-20200506-034655.log-2020-05-06 04:00:15.081 INFO SNAPSHOT_DELETE The snapshot tuchka at revision 776 has been removed
The graph for some reason went into a bad state too: