# Trash does not go away in 7 days **URL:** \ **Category:** troubleshooting\ **Tags:** trash\ **Created:** [April 23, 2024, 6:38pm UTC](https://forum.storj.io/t/trash-does-not-go-away-in-7-days/25936 "2024-04-23T18:38:27Z")\ **Posts on this page:** 9\ **Page:** 8
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [May 7, 2024, 6:12am UTC](https://forum.storj.io/t/trash-does-not-go-away-in-7-days/25936/148 "2024-05-07T06:12:42Z")
Seems the current workaround is: > [@When will trash update?](https://forum.storj.io/t/when-will-trash-update/26107/7): > > Turn the lazzy walker off by setting false in config or docker run. Turn the start up piece scan on, by setting it to true. Restart the node. Let it finish the walk; it can take days. The values will be updated. ---
**Author:** ![Vicente](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/vicente/32/1123_2.png) [@Vicente](https://forum.storj.io/u/Vicente)\ **Post date:** [May 8, 2024, 2:21am UTC](https://forum.storj.io/t/trash-does-not-go-away-in-7-days/25936/149 "2024-05-08T02:21:24Z")
I have the same problem on two of my nodes Is this solution something permanent or something temporary? Can I leave this alone or do I have to change lazzy walker to true after a while? Would this be the correct configuration? pieces.enable-lazy-filewalker: false storage2.piece-scan-on-startup: true ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [May 10, 2024, 12:10pm UTC](https://forum.storj.io/t/trash-does-not-go-away-in-7-days/25936/150 "2024-05-10T12:10:36Z")
> [@Vicente](#): > > Is this solution something permanent or something temporary? something temporary > [@Vicente](#): > > Can I leave this alone or do I have to change lazzy walker to true after a while? Yes and you may change it back, when it would be fixed. You may track the release changes either on [our GitHub](https://github.com/storj/storj/releases) or here, [Search results for 'release preparation order:latest' - Storj Community Forum (official)](https://forum.storj.io/search?q=release%20preparation%20order%3Alatest) > [@Vicente](#): > > Would this be the correct configuration? > > pieces.enable-lazy-filewalker: false > storage2.piece-scan-on-startup: true yes ---
**Author:** ![Thecoolpeople](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/thecoolpeople/32/7829_2.png) [@Thecoolpeople](https://forum.storj.io/u/Thecoolpeople)\ **Post date:** [May 12, 2024, 10:50am UTC](https://forum.storj.io/t/trash-does-not-go-away-in-7-days/25936/151 "2024-05-12T10:50:00Z")
I have found a bug in my storj node. The trash reported from the dashboard is 194.72GB in size, but on the filesystem the trash folder is: Size 43.39 GB (46,589,713,717 Bytes). 252050 Files, 4163 Folder containing. The blob folder is 0.8TB in the dashboard, but in the filesystem it is Size: 749.56 GB (804,830,621,172 Bytes). 3866749 Files, 4100 Folder I think, this is ok, this referes to the rounding of the dashboard. So, what can I do to correct the trash size in the dashboard? The node is running at version 1.102.3 since 360h. no other bugs detected. (Default Docker container) Instead of reastarting the docker with the lazzy filewake. Is there a possibility of running a shell command in the docker directly without restarting and loosing downtime? ---
**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:** [May 12, 2024, 10:54am UTC](https://forum.storj.io/t/trash-does-not-go-away-in-7-days/25936/152 "2024-05-12T10:54:01Z")
> [@Thecoolpeople](#): > > The trash reported from the dashboard is 194.72GB in size, but on the filesystem the trash folder is: Size 43.39 GB (46,589,713,717 Bytes). Probably this is what you need to do: > [@Vicente](#): > > Would this be the correct configuration? > > pieces.enable-lazy-filewalker: false > storage2.piece-scan-on-startup: true ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [May 12, 2024, 10:56am UTC](https://forum.storj.io/t/trash-does-not-go-away-in-7-days/25936/153 "2024-05-12T10:56:02Z")
Yep, the workaround posted by @jammerdan should help. ---
**Author:** ![Thecoolpeople](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/thecoolpeople/32/7829_2.png) [@Thecoolpeople](https://forum.storj.io/u/Thecoolpeople)\ **Post date:** [May 12, 2024, 11:02am UTC](https://forum.storj.io/t/trash-does-not-go-away-in-7-days/25936/154 "2024-05-12T11:02:42Z")
But there is no shell command to do that inside the docker container? Which would be the docker ENV variables for that configuration, or will that problem be solved in 1.1.04.3, and if yes, when will the update be out? ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [May 12, 2024, 11:07am UTC](https://forum.storj.io/t/trash-does-not-go-away-in-7-days/25936/155 "2024-05-12T11:07:02Z")
You can. Just put these options after the image name, i.e.: ```auto docker run .... \ storjlabs/storagenode:latest \ --pieces.enable-lazy-filewalker=false ``` > [@Thecoolpeople](#): > > or will that problem be solved in 1.1.04.3 I hope so. I cannot track, because there is no issue on the GitHub. ---
**Author:** ![littleskunk](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/littleskunk/32/63_2.png) [@littleskunk](https://forum.storj.io/u/littleskunk)\ **Post date:** [May 12, 2024, 1:24pm UTC](https://forum.storj.io/t/trash-does-not-go-away-in-7-days/25936/156 "2024-05-12T13:24:27Z")
> [@Alexey](#): > > I cannot track, because there is no issue on the GitHub. > > > The new lazy filewalker works great. It moves a lot of data in a short amount of… time with no impact on my success rate. Thank you for all these improvements. > > There is one small issue. Since the trash cleanup was modified to run the lazy filewalker as well it doesn't update the used space / free space values. So once per week the storage node will move let's say 500 GB out of 5 TB into trash and update the cache. Total space used 5 TB. One week later the node has grown another 500 GB and once again it moves 500 GB into the trash folder. > Expected size: 4.5 TB used + 500 GB trash = 5 TB total. Actual size: 4.5 TB used + 1 TB trash. The cleanup job deletes the data from trash without updating the cache. [Previous page](https://forum.storj.io/t/trash-does-not-go-away-in-7-days/25936.md?page=7)