bug#11406: Bug? df uses f_bsize instead of f_frsize to calculate file system sizes

[Paul Eggert]

On 05/04/2012 07:23 PM, Nikolaus Rath wrote:
> # strace -v src/df -h ~/tmp/mnt
> [...]
> stat("/home/nikratio/tmp/mnt", {st_dev=makedev(0, 23), st_ino=1, 
> st_mode=S_IFDIR|0755, st_nlink=1, st_uid=1000, st_gid=1000, 
> st_blksize=131072, st_blocks=0, st_size=0, st_atime=2012/05/04-22:13:30, 
> st_mtime=2012/05/04-22:13:18, st_ctime=2012/05/04-22:13:18}) = 0
> statfs("/home/nikratio/tmp/mnt", {f_type=0x65735546, f_bsize=81920, 
> f_blocks=104857, f_bfree=104854, f_bavail=104854, f_files=1000000, 
> f_ffree=999994, f_fsid={0, 0}, f_namelen=0, f_frsize=10485760}) = 0

Sorry, I've lost context here.  What's wrong with those numbers,
or with the output of df?

The numbers indicate a file system with 104857 blocks, each of size
81920 bytes, for a total of 8,589,885,440 bytes.  Are those
numbers wrong?  If so, it's a problem with the kernel or the
file system, not with df.  And if the numbers are correct,
then what's wrong with df's behavior (you didn't say what
it was...)?