The 2.1.0.112 release notice details changes, but none that look clearly relevant.
This deadlock is very solid. I just tested a different version, manually setting DB’s repair-in-progress to true. Repair won’t run because it’s properly concerned about trimming destination files to match what might be a partial database. We’ve discussed list-broken-files and purge-broken-files, but what I feel they’re misreporting is when they say nothing’s broken. I deleted (one at a time) a dlist, dindex, and dblock file (which was the only dblock, and it certainly broke files).
My hope had been that if I could break something, it would notice, and so proceed.
I suppose we could try to get a clean Recreate. This is where downloading the files locally would be nice (keeping an original copy and one where we can experiment).
This is the kind of setup I had on the big mess I cited on my own backup. A way to avoid two local copies is to rclone sync from destination when doing another run.
I’d like to wait for dev advice, but response (not just here) has been behind recently.