I'm using rclone to transfer data from restic to a GDrive backend, and it usually works without any hickups.
However, I was running a restic prune operation to fix a few errors inside the restic repository, which takes some time.. a really really long time since restic is reading ~3.5TB of data that is placed within that repository.
Without going into details, restics long processingtime is divided into the following phases:
Phase 1 where restic reads all data and checks the current index for its packs took just over 52 hours.
Phase 2 there restic removes any unused data in older snapshots took around 19 minutes
Phase 3 where restic rewrites packs to actually remove the data took 7 minutes
Phase 4 where restic rebuilds the updated index for its packs was running in its 22nd hour (around 40% complete) when suddenly the operation stopped and this was logged:
rclone: Exception 0xc0000006 0x0 0x167145c 0x452e95
and everything stops and restic just aborts.
This is using restic v0.9.5 and rclone 1.47 running on 64bit Windows.
I have no log apart from a few lines that restic logged, and I am hesitant to restart the operation since it will take another ~74 hours (at least) where I am unable to perform any other backups..
Due to the long runtime I am also worried about adding --log-file, --log-format, --log-level and -v since it will probably generate a vast amount of logging that is more or less useless.
Please advice how/what I can do to debug the issue or how I can record some resonable and useful amount of logging..