Question for you all who know way more about it than I do.
I have a 10TB (labeled) HDD on my primary node. Storagenode says that my allocated limit has been reached. In my docker run command I have the following -e STORAGE=“8.0TB”. I selected this limit based on the fact that when I run “df -h” the HDD shows 9.1T of usable space. Then since it’s recommended to leave ~10% overhead, I rounded down to 8.0TB for the limit.
My question though is that my current df -h and df -H reports that my drive is about 80% full:
Then my CLI dashboard shows the following:
And my web dashboard shows the following:
As I believe I’ve read that Storj calculated the allowable storage space in TiB, so since my limit is set to 8.0TB in run command, I guess that lines up with the 8.0T used in the “df -H”. Although, I’m then confused as to why a 10TB drive would read out as 11T in “df -H”.
Then, I’m confused as to why the CLI dashboard says that 8.1TB is used, and then the web dashboard says that there’s >350GB disk space remaining (of the 8TB limit from the run command)…
Anyone have any insight to the situation I’m seeing?
Also, I guess I’ll go ahead and ask, with the information I’ve presented, what could I safely increase my run command limit to? I’m assuming at least 8.2TB and still have that ~10% overhead.