I am running 2 nodes on a win10 machine. One is a 3TB (2.72TB actual space) and an 8TB (7.27TB actual space) nodes. The 3TB I have allocated 2.5TB for the node leaving 200gb just in case and 7TB allocated for the 8TB node.
Now on the dashboard, my 2.5TB is reported as fully used up:
But on windows explorer:
You can see it says there is 450GB free (that’s with the 200 I left free, so a total of 250GB isn’t being filled/seen by Storj?)
Similar story for my 8TB drive, windows says I have 3.93TB free (meaning Storj is using 7.27-3.93 = 3.33 TB - if my math isn’t dum).
But on the dashboard it’s reported as 3.64TB so that also doesn’t add up.
Storj use not binary base space but on base of decimal. But windows show on base on Binary.
In decimal Disk is 3000 MB but in Binary it is 2720 MB
You can seach in google why it is so different.
You easily can give to node 2.7 TB and there will be also free space. I use it like that.
Okay, that explains a part of it- and I updated my original post with my 8TB node - how come Storj reports using more space than Windows in that case? If Storj uses binary representation, then Windows should report a higher number of space used right?
% units
3675 units, 109 prefixes, 114 nonlinear units
Windows reports as taken (TiB, GiB are the base-2 units):
You have: 2.72 TiB - 450 GiB
You want: GiB
* 2335.28
Storj node reports as taken (TB is the base-10 unit):
You have: 2.49 TB
You want: GiB
* 2318.9932
The difference of 16 GiB can probably be explained by the amount of file system metadata (like storing file names, directories) Storj is unaware of, but Windows is. I don’t know what kind of overhead NTFS has, but I’ve observed similar overhead on ext4 on Linux, so I find it believable.
Same with your other drive. Windows reports:
You have: 7.27 TiB - 3.93 TiB
You want: GiB
* 3420.16
Storj node reports:
You have: 3.64 TB
You want: GiB
* 3390.0142
Blame Microsoft for not switching to base-10 units like everyone else.
