So, the change to turn off GC went out on 6/26, and we only put together that this problem was happening because of GC on 6/30. Unfortunate!
That said, I didn’t think the piece count problem was very widespread among nodes, but looking at the database it does seem to be a large fraction. I should have done the diligence to check that earlier. Thanks for bringing it up.
We’re current brainstorming some ideas for stop-gap measures before the deploy, and I’ll update if we end up with something.
update: One time update of node piece counts · Issue #6025 · storj/storj · GitHub is tracking the temporary fix before the permanent fix is deployed.