# Disk space cleanup

**URL:** <https://meta.discourse.org/t/disk-space-cleanup/301984>\
**Category:** Self-hosting\
**Tags:** server-resources\
**Created:** [April 2, 2024, 4:05am UTC](https://meta.discourse.org/t/disk-space-cleanup/301984 "2024-04-02T04:05:51Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![CT075](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ct075/32/375367_2.png) [@CT075](https://meta.discourse.org/u/CT075)\
**Post date:** [April 2, 2024, 4:05am UTC](https://meta.discourse.org/t/disk-space-cleanup/301984/1 "2024-04-02T04:05:51Z")

</div>

I run an old forum (~10 years, 200k posts) that has been running into some chronic disk issues. At the moment, we’re not in imminent danger of the lights going out, but we have reached the point where I’m getting daily messages about backups failing due to no disk space (the backup process itself seems to take like 10 gigabytes of disk, which fails if we already have a backup on-server).

Is there anything I can do to stem this tide a little?

I accept that disk space is one of those things I have to deal with as time goes on and do plan to upgrade eventually, but I’m wondering if there are other ways to buy time via compression, or just some cleanup of files that I haven’t thought to check.

I have already run `./launcher cleanup` (0B saved), and have attached a snapshot of the db stats.

[db\_stats.txt](https://meta.discourse.org/uploads/short-url/opD938QJ0yh1TmvygO4QLC8wZil.txt) (17.7 KB)

---

_[View the full topic](https://meta.discourse.org/t/disk-space-cleanup/301984)._
