# Loop stacktrace discovered in 4MB line in storagenode logs that resulted in a crashed node **URL:** \ **Category:** troubleshooting\ **Tags:** windows-gui\ **Created:** [June 21, 2024, 3:19am UTC](https://forum.storj.io/t/loop-stacktrace-discovered-in-4mb-line-in-storagenode-logs-that-resulted-in-a-crashed-node/26738 "2024-06-21T03:19:35Z")\ **Posts on this page:** 3\ **Page:** 2
**Author:** ![jolmando](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/jolmando/32/7824_2.png) [@jolmando](https://forum.storj.io/u/jolmando)\ **Post date:** [June 23, 2024, 6:50pm UTC](https://forum.storj.io/t/loop-stacktrace-discovered-in-4mb-line-in-storagenode-logs-that-resulted-in-a-crashed-node/26738/22 "2024-06-23T18:50:33Z")
from what I tested this week, the node is not suitable for such settings. One disk node is now not very good. With just one node down, all the others start to experience high latency. The io is being loaded and the delay is increasing, other drives are queuing up πŸ™‚ storj gets to the point where it needs an already powerful file system to handle such loads. But destroying ssd/nvme for such a price is not profitable. Therefore, I hope for optimization in the future. the node slows down, both on a $500 disk and on a $100 disk πŸ™‚ in any case, with such a load, an ssd/nvme cache is needed. and these are already additional constant costs πŸ™‚ ---
**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:** [June 24, 2024, 4:34am UTC](https://forum.storj.io/t/loop-stacktrace-discovered-in-4mb-line-in-storagenode-logs-that-resulted-in-a-crashed-node/26738/23 "2024-06-24T04:34:36Z")
> [@loueradun](#): > > `timed out after 1m0s while verifying writability of storage directory` yes, the same error as before. Did you try to optimize the filesystem? > [@loueradun](#): > > It seems like a monitor for failing uploads/downloads which decreases the connections until things settle would be appropriate IMHO, but to be fair, I’m not intricately familiar with how the jobs are executed. This is already implemented in the node selection: > [@Updates on Test Data](https://forum.storj.io/t/updates-on-test-data/26034/313): > > Ok while you are removing any concurrency limit you might have set I will explain how the node selection actually works. When a segment gets commited to the database it will contain the nodes that have been fast enough and it will be missing the nodes that got long tail canceld. The satellite calculates a success rate for each node with that. The node selection takes that success rate. Instead of 110 total nodes it selectes 220 nodes at first and compares them in pairs and pick the one with th… ---
**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:** [June 24, 2024, 4:40am UTC](https://forum.storj.io/t/loop-stacktrace-discovered-in-4mb-line-in-storagenode-logs-that-resulted-in-a-crashed-node/26738/24 "2024-06-24T04:40:46Z")
> [@jolmando](#): > > the node slows down, both on a $500 disk and on a $100 disk πŸ™‚ in any case, with such a load, an ssd/nvme cache is needed. and these are already additional constant costs πŸ™‚ You can increase a check timeout, if you know that your HW is ok, just cannot keep up with the load. One disk systems are still can work (all my three nodes are configured as one node per disk and they still can work without an SSD cache), but perhaps not all setups. Unfortunately I cannot check on my Pi3 now, it cannot boot anymore (the SD card is failed), but it’s in another country, I do not know when I could be able to fix it. So I just switched it off by a smart plug. [Previous page](https://forum.storj.io/t/loop-stacktrace-discovered-in-4mb-line-in-storagenode-logs-that-resulted-in-a-crashed-node/26738.md?page=1)