# Is 30GB now too small to upgrade?

**URL:** <https://meta.discourse.org/t/is-30gb-now-too-small-to-upgrade/90435>\
**Category:** Self-hosting\
**Created:** [21 ביוני,‏ 2018,‏ 11:51pm UTC](https://meta.discourse.org/t/is-30gb-now-too-small-to-upgrade/90435 "2018-06-21T23:51:31Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Amicable](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/amicable/32/68902_2.png) [@Amicable](https://meta.discourse.org/u/Amicable)\
**Post date:** [22 ביוני,‏ 2018,‏ 8:36am UTC](https://meta.discourse.org/t/is-30gb-now-too-small-to-upgrade/90435/3 "2018-06-22T08:36:05Z")

</div>

Thank you very much @codinghorror . Docker cleanup gave me back 6 GB or so & the Ubuntu cleanup showed up plenty of old kernels, so another 4GB or so. It’s now maintainable:

```
Filesystem 1K-blocks Used Available Use% Mounted on
udev 487940 0 487940 0% /dev
tmpfs 101608 10880 90728 11% /run
/dev/vda1 30428648 14770996 15641268 49% /
tmpfs 508028 1028 507000 1% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 508028 0 508028 0% /sys/fs/cgroup
tmpfs 101608 0 101608 0% /run/user/0
none 30428648 14770996 15641268 49% /var/lib/docker/aufs/mnt/800
shm 524288 8 524280 1% /var/lib/docker/containers/618

```

Doing this manually once a year or so seems painless enough, but could I configure unattended upgrades to deal with the kernels & docker? Is this wise on an instance that does nothing but run vanilla Discourse or might it conflict with Discourse upgrade scripts?

---

_[View the full topic](https://meta.discourse.org/t/is-30gb-now-too-small-to-upgrade/90435)._
