Bug #3793
closedwrong size reported in some distributions/toolchains
0%
Description
In ceph_statfs we set f_bsize to be 1MB in order to report very large available spaces. However, nowadays it is apparently correct to set to set f_bsize to the "optimal transfer size" and to use f_frsize (the "fundamental block size" instead of f_bsize's "block size") as the actual block size to use alongside the blocks free/used/available reporting.
In some newer toolchains this means our free space is reported incorrectly; see eg df from corutils 8.20 versus that in corutils 8.13 (from Debian; thanks dwm37!).
Presumably that means we want to set f_frsize to 1MB — but do we then want to reduce the f_bsize since 1MB transfers really aren't necessary? I'd guess that older tools will break themselves if we reduce f_bsize since they appear to be using it right now, so we probably shouldn't do that. And hopefully simply updating the f_frsize won't break anybody, but we should check this on a range of distros before distributing it.