Ok this is deeply weird. I log back into my mastodon instance and AGAIN it is using 77% disk. In spite of the fact it was below 50% yesterday. What is going on?
something is 'rebuilding' after i clear it out. I am running a prune-profiles again... see how much that trashes.
so i rerun media remove --days=7 --prune-profiles and it knocks out 247MB.
I'll rerun it with --days=2 or something ... Am I not comprehending what this command does or something?
If it helps, I use:
```
#!/bin/bash
PATH=/home/mastodon/.rbenv/shims:/home/mastodon/.rbenv/bin:/usr/local/bin:/usr/bin:/bin
# Prune remote accounts that never interacted with a local user
RAILS_ENV=production /home/mastodon/live/bin/tootctl accounts prune;
# Remove remote statuses that local users never interacted with older than 2 days
RAILS_ENV=production /home/mastodon/live/bin/tootctl statuses remove --days 1;
# Remove media attachments older than 1 days
RAILS_ENV=production /home/mastodon/live/bin/tootctl media remove --days 1;
# Remove all headers (including people I follow)
RAILS_ENV=production /home/mastodon/live/bin/tootctl media remove --remove-headers --include-follows --days 1;
# Remove link previews older than 1 days
RAILS_ENV=production /home/mastodon/live/bin/tootctl preview_cards remove --days 1;
# Remove files not link to any post
RAILS_ENV=production /home/mastodon/live/bin/tootctl media remove-orphans;
```
@neil i do have some of that in place, but not all. What puzzles me is how this gigantic disk usage re-spawns? The follow up question is, even with your script there, is your setup almost working against itself - if you see what I mean? There is something constantly trying to eat disk space, but then your scripts are reigning it in, but not necessarily STOPPING the root cause?