# Tombstone directory not getting cleaned up for images

**URL:** <https://meta.discourse.org/t/tombstone-directory-not-getting-cleaned-up-for-images/106575>\
**Category:** Product Support\
**Created:** [January 15, 2019, 10:42am UTC](https://meta.discourse.org/t/tombstone-directory-not-getting-cleaned-up-for-images/106575 "2019-01-15T10:42:52Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [January 15, 2019, 7:09pm UTC](https://meta.discourse.org/t/tombstone-directory-not-getting-cleaned-up-for-images/106575/2 "2019-01-15T19:09:12Z")

</div>

I think that you could just `rm -r tombstone` and the directories will get created as needed when more tombstoned files get moved over. A slightly more paranoid solution would be something like

```
find tombstone -type f -exec rm \{\} \;

```

Still more paranoid would be to first rsync the tombstone stuff elsewhere for a while (just in case something got tomestoned by mistake).

The most robust (but scary nonetheless) solution would be to move images to S3 (AWS, or Digital Ocean). It looks like it’d be $5/month for 250GB on Digital Ocean. It’s probably a good long term solution and will reduce load on your server.

---

_[View the full topic](https://meta.discourse.org/t/tombstone-directory-not-getting-cleaned-up-for-images/106575)._