[BUG] Incorrect storage usage reported in Running Status for deployment with 4 nodes

[dmitrygribenchuk]

Describe the bug
I have a RustFS deployment running in distributed mode with 4 nodes (v1.0.0-beta.8).

After uploading data, the Running Status page reports: Used capacity: 1.8 TB

This looks incorrect because the physical disks are actually almost full.

However, when checking the Rebalance page, the reported usage is: Used capacity: 3.6 TB

The 3.6 TB value matches the real consumed space on the disks.

So there is a discrepancy between:

Running Status storage usage
Rebalance storage usage

The Running Status page seems to report only the logical/user data size (or data after erasure coding calculation), while Rebalance shows the actual physical disk usage.

Disk usage on all nodes

All 4 servers have the same disk occupancy.

Example from one of the nodes:

root@debian:~# df -h /media/rustfs-01
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdd        1.9T  1.9T  7.1G 100% /media/rustfs-01

Expected behavior

The storage usage displayed in Running Status should match the actual consumed disk space, or at least clearly indicate whether the value is:

logical data size
physical disk usage after erasure coding overhead

Actual behavior
Running Status shows: 1.8 TB used
while the real disk usage is: 3.6 TB used

This can be misleading because it looks like there is still a lot of free space available, while the cluster is actually near full capacity.

Screenshots

Configuration:

4 nodes
1 disk per node
2 TB disk capacity per node

After restart all nodes console starts showing more used space than actually is.: