I’m gonna have to agree with this @clement . If the downgrades are indeed what caused this, it can’t be up to SNOs to fix this. And it really sucks that despite warnings from us (including me) about the wrong minimum version on versions.storj.io, very early in that upgrade cycle, you did nothing to prevent those downgrades. And in fact, the same issue happened again on the next rollout. Which btw, if it happens when rolling out 1.105, downgrading nodes from 1.104 will instantly break them due to the database migration. So I certainly hope this is now permanently fixed.
The downgrades weren’t caused by SNOs. And for every SNO passionate enough to pay attention and post here, there will be at least 5-10 more not paying attention and left with trash that will never be removed. So this clean up is up to you now. Though please find an approach that doesn’t involve stopping bloom filters. We still need those badly as many nodes still have large amounts of uncollected trash.