# Space issues, recent

**URL:** https://meta.discourse.org/t/space-issues-recent/63948
**Category:** Feature
**Created:** [June 5, 2017, 11:59am UTC](https://meta.discourse.org/t/space-issues-recent/63948 "2017-06-05T11:59:07Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [June 13, 2017, 11:12pm UTC](https://meta.discourse.org/t/space-issues-recent/63948/6 "2017-06-13T23:12:35Z")

</div>

> [@JagWaugh](#):
>
> 5GB should be enough headroom for the update, at least for a while.

Cool. I just made the script use the correct docker storage path, when a user customize it.

> [@JagWaugh](#):
>
> I would suggest warn and exit if less than that is fine, but I think it might make sense to get the size of the last backup, and if (after the update) there won’t be enough space for the next backup, then at least warn, or better yet give them the choice.

I think this should be an warning in the app, possibly an extension to [this](https://meta.discourse.org/t/if-automatic-backup-fails-there-should-be-a-warning/64461).

---

_[View the full topic](https://meta.discourse.org/t/space-issues-recent/63948)._