The docker’s overlay filesystem may revert your changes if the container is not removed before the change.
Please give me the algorithm for creating a new node for Hashstore.
I thought the network was already set for any new data to go into hashstore? If so… then every new node is a new node for hashstore. Just do a normal install.
I believe we’re waiting for Storj to start pushing migration of data on old nodes to hashstore.
1 Like
Start the node as usual, than activate passive and active migration. Wait 1 day. Clean the blobs folder. Bam! You are on hashstore with a fresh new node. 
New nodes still start on piecestore.
1 Like
You both with @Roxor are correct. The new nodes starts on piecestore, but they will receive a command from the satellite to use hashstore for any new pieces on the next check-in.
@max232 You can just start with the new node and do nothing, or do like @snorkel is suggested.
1 Like
3 posts were split to a new topic: Multinode is failed to fetch node version
Do I understand correctly that old nodes in new versions migrate to the hashstore themselves?
When Storj is comfortable with the software quality: they’ll be able to slowly toggle old nodes to begin active-migration to hashstore. Right now old data is left in piecestore, and new data (on all nodes) is going into hashstore.
I don’t see a big benefit of forcing active-migration early: knowing I can “just wait” (and perhaps avoid some early bugs) and it will happen automatically.
3 Likes