The bug is fixed but it doesn’t correct the numbers the previous releases messed up. You have to run the piece scan on startup once to correct the numbers and from there on the bug fix should keep it correct.
1 Like
I don’t get it.
I updated to 1.104.1 and run used-space an all nodes. Some nodes went straight to 1.104.5 because by the time I got to updating them, that version was live.
So…yea. Does that require yet another used-space after 1.105? I see the fix in that as well.
Not that I would be aware of. I didn’t notice any mistakes on my node.
@littleskunk
(20 characters)
Version 1.104.1 nodes still having uploads and downloads but I can not restart the node because of version check.
Should it be like this or is it a bug to get uploads/downloads with outdatet version?
That’s normal behavior. If the minimum is updated, then nodes on the network can’t be just “shoved off”. They need time to update.
If on the other hand you want to (re)start a node with anything less than the minimum, then yea, that node needs to update first.
1 Like
The issue is not closed 
1 Like