Seeing this on both my nodes. I did set the usable storage down to 2TB / 3TB respecively a few weeks because I needed to reclaim some storage, but figured this would happen over time and not all on the same day. It also dropped way below the threshold. Both nodes down to about 500gb.
The “Average Disk Space Used This Month” comes from the satellite: and the US one is undergoing maintenance. Stats for it have basically been wrong since the start of July.
I’d ignore it: your Allocated Disk Space → Used Other number will still be close to what the satellite is actually tracking internally. But yeah Used-Space has been contracting in general.
Could you please check, which satellite didn’t send statistics?
US satellite is showing 0B for me the last few days. Went from 8.5TB to 0b
Why would it affect anything, let alone payout?!
As I keep repeating, ignore the dashboard. It’s 100% noise. Focus on keeping mode online and data intact. This is where your responsibility ends and stroj-es begins.
Because the disk usage statistics show a much lower payout, too.
Estimations or the payout history? Does the history match your actual disk usage?
This is coming from the same faulty data source. Ignore it. Satellite is responsible for billing. What node thinks is irrelevant and always incorrect: for example, node cannot know if it won the race for the specifc piece or not. So it cannot possiblly know whether it will be paid for that piece or not. Satellite — does.
Trust the process. Not dashboard.
There could be another issue with the storage database, like here: Disk usage discrepancy? - #1254 by mr.Viking
That’s a good question! Last month I didn’t have this issue. In this case I’m only referring to the estimate. So the two aren’t the same thing? Is the actual payout completely independent from this?
Oh, thank you. I thought the value shown on the dashboard was the actual amount and that the billing was based on that.
There is a migration ongoing. We are switching over to TiDB.
Its a bit more tricky. On the satellite side a missing tally result will just roll over to the next one. Lets say you are holding 1 TB but tally doesn’t track that for 3 days. On the 4th day tally would run, find out that its last runtime was 4 days ago and write 4 days * 24 hours * 1 TB in the database. At that point your payout will be correct.
The dashboard on the other hand would have to backfill the missing datapoints. Maybe one day someone will fix it. It is not the highest priority as long as the payout is not impacted.
Correct except for data that was deleted or timed out during those 4 days. Or am I missing something… 
Same is correct for the other direction. Any new upload will be accounted for the full duration as well.
Thanks for the information.
Will there be engineer post about how to migrate database 
?