Available space 0MiB for path `/root/.local/share/subspace-node/chains/subspace_gemini_3g/paritydb/full


Node has been working 2 months without any problem. I haven’t event touched it.
Yesterday accidently appeared this error. Parameters were the set in the beginning when created the node (2 months ago).

Any suggestions what has happened?


2023-12-17T21:39:09.098517Z [Consensus] 💻 Memory: 15615MB
2023-12-17T21:39:09.098519Z [Consensus] 💻 Kernel: 5.4.0-169-generic
2023-12-17T21:39:09.098519Z [Consensus] 💻 Linux distribution: Ubuntu 20.04.6 LTS
2023-12-17T21:39:09.098520Z [Consensus] 💻 Virtual machine: yes
2023-12-17T21:39:09.098551Z [Consensus] 📦 Highest known block at #678802
2023-12-17T21:39:09.098931Z [Consensus] Running JSON-RPC server: addr=, allowed origins=["http://localhost:*", "*", "https://localhost:*", "*", "https://polkadot.js.org"]
2023-12-17T21:39:09.099139Z Available space 0MiB for path `/root/.local/share/subspace-node/chains/subspace_gemini_3g/paritydb/full` dropped below threshold: 1024MiB , terminating...
Error: SubstrateService(Other("Failed to start storage monitor: StorageOutOfSpace(0, 1024)"))
subspaced.service: Main process exited, code=exited, status=1/FAILURE
subspaced.service: Failed with result 'exit-code'.
subspaced.service: Scheduled restart job, restart counter is at 29.
Stopped Subspace Node.

Error says you ran out of free disk space

So, 2 months it was enough space and accidently it runs out of it. It uses 120 Gb from 160 disk Gb, and server is dedicated only for this node. If it is possible, ok.
What can you recommend, to wipe everything and to deploy node again? Or any other solutions?


The node will not use significantly less space I’m afraid. You can try to decrease farm size or see if there is anything else using significant amount of space. 120GB is on the lower end of the spectrum and node is not using as little space as it should just yet (see Make node use bounded amount of space on disk · Issue #2114 · subspace/subspace · GitHub).

1 Like