Am I the only one who thinks this is inconsistent?

Node Operators FAQ
1

The very same node running with Docker command "Env": ["STORAGE=5TB"

From the api:

"diskSpace":{"used":4678473482752,"available":5000000000000,"trash":254512924544,"overused":0}

From the multinode dashboard:

NODE DISK SPACE USED DISK SPACE LEFT
01 4.93TB 451.39MB

From the multinode disk section:
Screenshot_2022-03-18_033537

From the node dashboard:
Screenshot_2022-03-18_033649

Grafana:

Node Disk Total Disk Trash Disk Used Disk left
01 5.000 TB 254.74 GB 4.678 TB 67.01 GB

And finally a df -H:

/dev/sda        5.1T  5.0T   23G 100% /mnt/storj

If you think this is consistent, then please explain to me the variance in values and more important, which will determine what the node will do?

2 Likes
2

You need to use

df -H
3

It is df -H, I’ll edit that in my post to make it clear:

df -H /dev/sda
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda        5.1T  5.0T   28G 100% /mnt/storj
1 Like
4

ah the wonders of storage when nobody can agree on a metric or point of view…
when using zfs one sort of gives up on accurate sizes… each thing sort of ends up having to many for one to really keep track lol.

looks like multinode might be in binary based storage enumerations and multinode must then be in decimal

gibibytes vs gigabytes

5

It’s not just that. The free remaining space is totally inconsistent as well.

2 Likes