Hashstore: bad file descriptor

Does this work - to put that data to SSD like we do with DBS currently ?

Cheers

any simple scripts / snippets you could give or what is needing to be added to the run command

No script or adding anything to the run command. I just moved the hashtable directory to the system drive and created a symbolic link to it in the required place in the storage directory

3 Likes

I believe the option to move the hashtables is in one of the new verions, 120+…

Did this as well and it brought the node back online

I did this too, and it worked.

Commands:

  1. mkdir -p data/storage/hashstore
  2. rsync -avhr /mnt/storj/data/storage/hashstore/ data/storage/hashstore
  3. Edit docker-compose.yml: Add in volumes:: - ./data/storage/hashstore:/app/config/storage/hashstore

I prefer this over symbolic links, because it is more obvious at first glance that I am overriding that one directory.

3 Likes