I think I figured it out -- since some consumers want the scaling to be powers of 10 instead of 2, it checks if the next largest suffix is larger than the value to scale to determine the correct suffix. So for exabyte values, it tries to see if the value to scale is smaller than a (somewhat ironically) zetabyte, which cannot fit in a 64-bit integer. I'll push an update with the fix in a few minutes to verify (I've recreated & tested it locally, but just to be sure).
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/openzfs/openzfs/pull/435#issuecomment-320013041 ------------------------------------------ openzfs-developer Archives: https://openzfs.topicbox.com/groups/developer/discussions/T1bb1d6d8ecb1936c-M41de5c4c7d11e4b90c2fa4d8 Powered by Topicbox: https://topicbox.com
