# 0.28.2 update causing node to use too much storage **URL:** \ **Category:** troubleshooting\ **Created:** [December 19, 2019, 10:58pm UTC](https://forum.storj.io/t/0-28-2-update-causing-node-to-use-too-much-storage/3289 "2019-12-19T22:58:25Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Quantum64](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/quantum64/32/62_2.png) [@Quantum64](https://forum.storj.io/u/Quantum64)\ **Post date:** [December 19, 2019, 10:58pm UTC](https://forum.storj.io/t/0-28-2-update-causing-node-to-use-too-much-storage/3289/1 "2019-12-19T22:58:25Z")
My node was full and not receiving any more data as expected until the most recent update, where it started downloading additional data even though there is no available space. How can I stop this before the disk fills up? ![image](https://storj-s3.bcdn.literatehosting.net/original/2X/4/4d51ef8a80b0082ba5515962b212c15498f25907.png) ---
**Author:** ![pony](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/pony/32/65_2.png) [@pony](https://forum.storj.io/u/pony)\ **Post date:** [December 20, 2019, 3:29am UTC](https://forum.storj.io/t/0-28-2-update-causing-node-to-use-too-much-storage/3289/2 "2019-12-20T03:29:45Z")
Fierce You can use 150gb extra When the node was installed Set the disk space value for the node Did it become a decoration? I also have node disk full Over about 5MB I’m still waiting for version 0.28.2 to automatically delete invalid data It seems to take five days to wait, according to the official > [@Changelog v0.28.2](https://forum.storj.io/t/changelog-v0-28-2/3251): > > Garbage Collection Every 5 days the satellite will send a bloomfilter to the storage node. The storage node will use it to identify garbage pieces. In the storage node log you will notice a few delete messages but on disk the space will still be used for additional 7 days. The logging is currently missleading. First we move the pieces into a trash folder and 7 days later we delete it without any additional log messages. If something goes wrong and the satellite sends empty bloomfilters we can… Waiting ---
**Author:** ![kevink](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kevink/32/6077_2.png) [@kevink](https://forum.storj.io/u/kevink)\ **Post date:** [December 20, 2019, 6:01am UTC](https://forum.storj.io/t/0-28-2-update-causing-node-to-use-too-much-storage/3289/3 "2019-12-20T06:01:53Z")
That seems to be the discovered trash, I have the same situation. But you did not download more pieces or use more space than before. Check your logs if you really think your node downloaded pieces. ---
**Author:** ![peem](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/peem/32/6323_2.png) [@peem](https://forum.storj.io/u/peem)\ **Post date:** [December 20, 2019, 8:18am UTC](https://forum.storj.io/t/0-28-2-update-causing-node-to-use-too-much-storage/3289/4 "2019-12-20T08:18:16Z")
I have full SN (linux, docker). I checked the SN folder “trash”, it had 2.5GB. On the dashboard: “Disk Space Remaining -44.71MB”. After doing: “docker stop -t 300 storagenode” and “docker start storagenode” on the dashboard: “Disk Space Remaining 2.51GB” and after several dozen minutes SN began to receive files again until these 2.51GB are exhausted, now on the dashboard is: " Disk Space Remaining 0.51KB " as if SN restart “forgot” about what it has in the “trash” SN folder. In my system only SN disk had 32.5GB of free space, now 30.1GB of free space. So I warn you - for full SNs do not restart SN for now … But what if the “watchtower” updates and reboots SN …? ---
**Author:** ![schnutzie](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/schnutzie/32/63_2.png) [@schnutzie](https://forum.storj.io/u/schnutzie)\ **Post date:** [December 20, 2019, 9:45am UTC](https://forum.storj.io/t/0-28-2-update-causing-node-to-use-too-much-storage/3289/5 "2019-12-20T09:45:52Z")
I hope the next watchtower update fix this problem. ---
**Author:** ![Norisz](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/norisz/32/71_2.png) [@Norisz](https://forum.storj.io/u/Norisz)\ **Post date:** [December 20, 2019, 11:44am UTC](https://forum.storj.io/t/0-28-2-update-causing-node-to-use-too-much-storage/3289/6 "2019-12-20T11:44:54Z")
I have the same issue, -120GB and my 900Gb was full before. ---
**Author:** ![heunland](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/heunland/32/6076_2.png) [@heunland](https://forum.storj.io/u/heunland)\ **Post date:** [December 20, 2019, 3:53pm UTC](https://forum.storj.io/t/0-28-2-update-causing-node-to-use-too-much-storage/3289/7 "2019-12-20T15:53:52Z")
> [@Changelog v0.28.2](https://forum.storj.io/t/changelog-v0-28-2/3251/11): > > Warning: Garbage collection is messing up the free space calculation. If your storage node is full and executes garbage collection it might accept more pieces than it has free space. At the end it will get disqualified. We are working on a fix. Please reduce your allocated size to make sure the storage node is not running into a crash. ---
**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:** [January 1, 2020, 1:49pm UTC](https://forum.storj.io/t/0-28-2-update-causing-node-to-use-too-much-storage/3289/8 "2020-01-01T13:49:44Z")
Bug is now fixed: > [@Changelog v0.28.4 (storage node only)](https://forum.storj.io/t/changelog-v0-28-4-storage-node-only/3456): > > Bugfix Storage Node used space calculation The used space calculation now takes the trash folder (garbage collection) into account.