Changelog v1.11.1

And I agree with you. I was just nitpicking because you said “it seems to be exact” :grin:

I think it’s now perfect as it is :+1:

By the way, the only reasons I configured my node with 894GB are:

  • my disk is a 984GB disk (Initially 1TB, but some corrupted sectors were isolated long ago, and no new corrupted sectors appeared so far…).
  • because of the way I calculate the 10% overhead to leave on disks as suggested by StorjLabs: I did 984/1.1 which gives 894: that’s what I allocated to the Node.
  • I did not know it was getting rounded up at the time.

That’s it :slight_smile:
I could probably safely go back to 900GB.

1 Like