ERROR lazyfilewalker.gc-filewalker.subprocess failed to save progress in the database

Do they? I have found other posts indicating that it doesn’t reach that. If that’s the case, then never mind, I guess full inodes IS required.

Yeah, just checked my documentation and I had it in my head that -T largefile4 reserved one inode per 4k. Nope, my bad. It’s one inode per 4 megs. Which is fine for chia and a lot of other storage based cryptos but not for Storj.

4 million files per TB would suggest an average file size of 250k.

I guess I misinterpreted some of what this post suggests, or else the proper setup requires tuning other parameters, not just raw inode count.