df -h and see which file system is taking up most of the disk space and then try to narrow down the scope with du -h with an optional --max-depth=1 to find the offending file/folder. Another tool that you might want to checkout is ncdu
Thank you - yep, we do that and it certainly does stop the bumps. I’ll double check for sure, but also did want to just see if there was a quota/report per user as well - especially as it was within the Discourse backup.tar.gz.
max image size kb
The maximum image upload size in kB. This must be configured in nginx (client_max_body_size) / apache or proxy as well.
max attachment size kb
The maximum attachment files upload size in kB. This must be configured in nginx (client_max_body_size) / apache or proxy as well.
Or is this a member doing a mess of smaller uploads?
^ That. Our max image size was left at 3072 kb. It looks like just over a year of constant screen-shot uploading, but we are still figuring that out. It doesn’t look malicious, just really keen/dedicated and we are a very screenshot-centric forum. One tutorial topic alone had over 100 images uploaded. An interesting thing is the 2nd place uploader has only 0.6 GB used, so we’ll talk to who is doing it and figure something better out.
I wonder if the trust_levels could have a file/image quota added? I haven’t searched through the feature wishlist to find out as yet. This user is a level_3.
EDIT: I added a feature idea here, if others might have the need too:
I recognize the filenames repeated I think, and am pretty sure this was a bulk upload of screenshots either in a topic post or in a personal message. The size of the files (all .png’s) is like ‘595934 bytes’ or ‘322155’ as in, not files that look like they have been processed to thumbs or are avatars.
EDIT: We should move the discussion to the new bug topic I think, as I’m filling out the details as I find them there.
on my site it turned out to be backups that take up all the space. I’ve now changed it to only keep 3 on server, and the rest on s3. I also turned off “s3 disable cleanup” which means I can decide myself which backups there to keep.