# Why trash not deleted

**URL:** <https://forum.storj.io/t/why-trash-not-deleted/27122>\
**Category:** troubleshooting\
**Tags:** trash\
**Created:** [July 15, 2024, 3:31am UTC](https://forum.storj.io/t/why-trash-not-deleted/27122 "2024-07-15T03:31:01Z")\
**Posts on this page:** 1\
**Showing post:** 41

<div class="post-metadata">

**Author:** ![jammerdan](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/jammerdan/32/1121_2.png) [@jammerdan](https://forum.storj.io/u/jammerdan)\
**Post date:** [August 27, 2024, 5:08am UTC](https://forum.storj.io/t/why-trash-not-deleted/27122/41 "2024-08-27T05:08:57Z")

</div>

> [@Alexey](#):
>
> I still didn’t get your concern. The node can delete X amount of data per hour, independently of the order. The sort order will not change it, but it may slow down it, because first the node should execute a stat recursively (to get a modification date), order pieces by the modification date and then process the deletion

Why would it have to do that? I thought:

> [@Current situation with garbage collection](https://forum.storj.io/t/current-situation-with-garbage-collection/25711/155):
>
> Nested date folders in trash makes it very easy to purge old trash data. You don’t need to check each trash files on by one for the deletion time (which is the creation date of the trashed file). You can just delete folders which are old enough…

I am talking about the order of processing the date folders and it seems easy to tell the system to delete the oldest folder first?  
So in my example above, it should start with date folder 2024-07-05 until it is completely deleted, then next 2024-07-06 and so on. That is the sort order I am talking about.

---

_[View the full topic](https://forum.storj.io/t/why-trash-not-deleted/27122)._
