Hello Community, I see many Infos how to migrate to Hashstore. Is there one Document available with all Options, Settings and stuff ? When to restart the node ? Explanation of Environment Variables ? I try to collect and update this Thread: What is the current status of automatic migration? …

Okay, but if I understand correctly, we’re looking at a difference of about 200 GB for a node that has 2.83 TB of data + 170 GB of trash, which is quite a lot.

[image] nitrobass24: I’ve set this command which helped a bit and increased throughput to about 40mb/s There is not much we can do about migration speed. Even on full ssd nodes throughput was not higher.

It’s not linear. [image] CubeFan: 170 GB of trash Likely the not yet compacted garbage, the trash amount has an expiration date, after that date it will become ready for the compaction too.

[image] CubeFan: Okay, but if I understand correctly, we’re looking at a difference of about 200 GB My nodes on default settings are running at roughly 20% overhead above what node says. Node that I cleaned out with aggressive compaction settings, is slowly growing after returning to default…

Yes, I assume so, but I have taken the 170 GB of trash into account. du --si says that the node occupies 3.2 TB. The node says it occupies 2.83 TB and has 0.17 TB of trash. That leaves another 0.2 TB that is simply occupied, which I don’t understand. 3,2 - 2,83 - 0,17 = 0,2 So the node occupie…

[image] CubeFan: That leaves another 0.2 TB that is simply occupied, which I don’t understand. This is explained there: [image] Single node and multinode dashboards shows different values after migration to hashstore I think the single-node dashboard counts uncompacted garbage as free spa…

OK, thank you. Wouldn’t it be a good idea to let FileWalker determine the actual size occupied by the file system? Because the dashboard always displays incorrect values. I noticed something else, and I read somewhere that this is not good. I use Portainer to manage the node stacks. But when I sto…

[image] CubeFan: OK, thank you. Wouldn’t it be a good idea to let FileWalker determine the actual size occupied by the file system? It’s not used for hashstore. It will not be fixed. You may use a multinode dashboard, it will show the free space, which your node reporting to the satellites. T…

Then I’ll wait a week or two and see if the deviation decreases. Thank you. [image] Alexey: You need to specify a timeout to 300s. The clause under the service is stop_grace_period. I already have this in Docker Compose, so am I also safe with “terminated”? services: storj-node: …

[image] CubeFan: OK, thank you. Wouldn’t it be a good idea to let FileWalker determine the actual size occupied by the file system? +1 for the answer from Alexey, just adding some more details: One of the benefit of hashstore is eliminating all the walkers (other one is speed, as it can work…

Hashstore Migration Guide

Node Operators getting started

Alexey October 30, 2025, 7:12am 205

This is explained there: