Dashboard: Calculation error for "Disk space used This Month" and "Disk Average Month"?

This picture from the multinode dashboard, I have 4 nodes on different systems.
1 is Windows GUI, NTFS
2 and 3 are docker versions in Docker desktop for Windows, so NTFS again but via 9P Protocol (network filesystem)
4 is Raspberry Pi 3b+, ext4

why my used space only half of the real space,and the other 4nodes have the same problem

it`s v1.69.2

You are lucky…

v.1.70.2

You are using an older script. Try with the latest, ver. 12.3.1

What is your filesystem on this drive?
If it’s Windows, please show properties of this disk with usage. If it’s Linux, then use this command (please correct the path):

du -s --si --apparent-size /mnt/storj/storagenode

Any node updated to 1.70.2 shows wrong average disk space used this month graph

2 Likes

Confirmed, it’s not correct

I see this on one of my nodes, it’s updated to v1.70.2 and has this discrepancy.
Notified the team.
But perhaps it’s better to have an issue on our GitHub.

1 Like


it is my disk properties

Then it’s not related to the used filesystem, NTFS is a native filesystem for Windows, so discrepancy between amount of data and used space is not so great as if you would use exFAT.

Then I believe this is a bug in the new version of storagenode.

It seems the new version is buggy as you said…

No offline or anything from my end, no power outages.

There is already a thread for this - One day is missing

I see this on other node with 1.69.2, so is not the new version…

1 Like

I’m having this same problem, however it only shows incorrectly when I look at all satellites.
If I for say look at only US1, then it shows the correct amount of used space.

On my node v1.69.2 dashboard there are no errors. On v1.70.2 yes

For me, the graph flattened out the drop after 2 days. Now it shows normal on both versions.

Good hint, but just add the used space for all 6 satellites and divide by 6.
The “all satellites” used space is really just the average of all 6 satellites, not combined average.

2 Likes

v1.71.2 has the same Bug with Disk Space Used

Could you please add it to the issue?

Added it to the Github issue

1 Like