If piece-scan-on-startup is at false, a node operates and even have a good success score, but dashboard thinks it has 5TB free, but in fact it has 900GB, is there a safe mechanism regardless of what local dashboard says? Will the node stop filling before the real space ends? Or data will “fall o…

The node should report as full as soon as there not more than 5GB left (earlier this threshold was 500MB). [image] Upcoming storage node improvements including benchmark tool We also need to increase the free space buffer from 500MB to 5GB. Because of the TTL nodes will switch between full and f…

[image] Mitsos: when the node approaches ~5TB (seen it as low as 3.5TB) hm, I meant something different: it will reporting to the satellites that’s full, when it has less or equal than 5GB in the allocation/disk.

My bad on the wording. Yes that’s what I meant, when it’s at 5GB free it reports it to the satellite. Sometimes this overshoots (understandably) and it goes as low as 3.5GB. Will edit the values :sweat_smile:

oh? i see. i hope it really keep track of real disk space left, and do reports, im going to see for real if thats true i guess

Is this 5GB configurable? As it seems much more reliable than the 5-6days long filewalker in somecases

No, it’s hardcoded. And I didn’t get how is it related to the filewalker?

for me it took now about 6 days for the lazy walker to finish, and before this i restarted the node for config change, with the restart I lost more than a TB of used space on the dashboard, so even if i set the max space usable in the config to 7.6TB, my usage from 6.8TB dropped to like 5.7TB. And …

The filewalker may not succeed if you also have a databases related errors in your logs.

maybe, but still it is unreliable/slow under heavy load, and the phisical free space checks seems to be better as a failsafe, especially if the disk is dedicated to storj and the DB is moved to like an SSD in my opinion.

You may disable the lazy mode, then it will finish faster (however, it would likely affect the node’s success rate).

[image] redgyuf: maybe, but still it is unreliable/slow under heavy load Storj has become aware of this too luckily: Storage node performance for filewalker is still extremely slow on large nodes · Issue #6998 · storj/storj · GitHub So there is hope they are working something out. In my opi…

Storj Community Forum (official)

Is there a safe mechanism regardless of what local dashboard says?

Node Operators FAQ