# Fixing discourse after disk full

**URL:** https://meta.discourse.org/t/fixing-discourse-after-disk-full/165426
**Category:** Self-hosting
**Tags:** server-resources
**Created:** [September 25, 2020, 10:35pm UTC](https://meta.discourse.org/t/fixing-discourse-after-disk-full/165426 "2020-09-25T22:35:28Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [September 26, 2020, 12:06pm UTC](https://meta.discourse.org/t/fixing-discourse-after-disk-full/165426/4 "2020-09-26T12:06:27Z")

</div>

Just to note, Hetzner’s lowest tier offers only 20GB, but that’s been working for me. It can be worth tidying up the backups directory before trying an upgrade: having, of course, taken a new backup and copied it elsewhere for safety. (It’s a small forum: a backup is 120MB.)

In another case, I use Digital Ocean’s lowest tier, offering 25G, and in that case the forum’s backup comes in at 640MB.)

The one time I had trouble, it was the journal thing, but I cut that right down:

```
# journalctl --disk-usage
Archived and active journals take up 104.0M in the file system.

```

---

_[View the full topic](https://meta.discourse.org/t/fixing-discourse-after-disk-full/165426)._