It is a really good thought. Your comment prompted me to check the whole machine (SSD + raid array) and I don’t have any hard-linking of media files, torrent files or anything like that. So that isn’t it.

I think it’s just a bug in the system.

Not yet and hopefully I won’t have to do that.

Yeah, I thought about that too. It’s why I noted in the post that my files are set to delete and not be moved to the trash first. Those settings are in options/advanced.

I deleted .25 terabytes and it hasn’t changed at all. It used to increment up after every deletion, so this is new.

It doesn’t. I rolled the version back to 4.6.7 and it didn’t help, so I moved it forward again. Restarted the container, then the stack, then the whole physical machine. Nothing so far. Yeah, maybe I’ll file a report on their page.

Saving this for lots of use in the future.

Just so you know, the example docker compose file has /downloads as the only volume option for media. So I pointed the internal docker folder /downloads at my whole music library.

So you’re almost certainly banning people who are sharing their whole library if they are using the default docker compose file. For example, you would ban me by that rationale.