Disk usage discrepancy?

[support26]

@Alexey

please search for error and database, error and filewaker in your logs.
If you are on Windows (PowerShell):

Ok. Found several instances of error and database but filewaker was not found. Do you want the output of that command?

@Alexey

The current stat - what you would see on the dashboard. History, is what you can see in the Payout Info for this and previous months.

Would that be the Disk Utilization & Remaining? Some other user told me that would go back to what is was. Is that true?

@Alexey

When the customer want to upload a file, their uplink requests 110 nodes for each segment (64MiB or less) and start uploads in parallel. When the first 80 are finished - all remained got canceled. There you would see a lot of errors on PUT* requests, most of them “context canceled” or similar (because the uplink will not notify the losers, it will abruptly close remained connections).
The same for the downloads, but the customers’ uplink will requests 39 nodes and start downloads in parallel, when the first 29 are finished, all other will be canceled (they need only 29 pieces from the (current) 80 to reconstruct the file). You will get various errors on GET* requests in your logs in this case.
Both cases are called a long tail cancelations (cuts) to allow the customer to upload/download to/from the fastest nodes for their location.

Disclaimer: your node cannot be close to everyone customer in the world, so canceled uploads/downloads is a normal process.

I do not really understand that - but thanks for advising. Seems like I do not need to be concerned with the technical details as you note.