So for me the issue wasn't the media storage, that was only half full around 145GB of about 320GB. My issue was the database was growing so fast, primarily from relays. I was at around 32GB and had it reduced to 20GB.
Masto.host (npub18sk…l2gu) ran "tootctl status remove" on my instance, which had a huge impact as I was heavily using relays in the past, reducing the DB size by 1/3.
This is one of many reasons I am more than happy to keep using Mastohost as my provider :D