Upon further inspection of the disk space issue, we are actually not in the pickle I previously suspected. After digging in the main 64D user account, I noticed a huge discrepancy in the reported size of our user and games folders compared to the combined size of their parent folder:

There are only 4 directories under 64digits home folder, and the other two are under a gig, so something wasn't adding up. I ran `du` several times before getting to the verge of rage, when suddenly I noticed something funny in the output of `ls`. There was a file sitting right in the home folder that hadn't shown up in `du` because by default, `du` only lists directories and their combined sizes. The size of said file: 358,953,059,228 bytes (a.k.a. 335 GB). It was a log file (for apache's mod_rewrite). And it was being added to with every request made to the site.

Now, there's no need for such a verbose log unless a developer is actually reading it for debugging purposes. So I turned it off, and deleted the offensively large file. And thus, we went from 98% disk usage to 20%.

Short story short, we got our breathing room back. As long as no one leaves those logs on again, we should be fine on disk space for some time to come. And also, as the title suggests, we don't have to worry about deleting minecraft maps any time soon.

As a note to staff, Steven pointed out this isn't the first time we've encountered this very issue. Maybe it's time we set up a 64D admin log for keeping track of these recurring problems and their fixes, something that future staff can refer to when things start breaking. A bug tracker might work well for this.

And finally, sorry for those who got worried after the last blog in regards to the minecraft maps. We'll try to safeguard these chunks of 64D history as long as possible, and hopefully ensure copies remain available for anyone who is interested for a long time to come.