I had a customer with this issue, and It was a vvol that was 8,000 (or appeared to be) TB.
If we clicked on datastores it was the only datastore that threw this error.
I believe it can also happen when you have too many decimal points on a hard disk size, but internally searching our queue came up with one other customer that had this issue with vvols/datastores and being over 60TB.
Hit escape on the error instead of reload, open the datastores, sort by size and see which one throws the error may help.