bug#11406: Bug? df uses f_bsize instead of f_frsize to calculate file sy
From:
Paul Eggert
Subject:
bug#11406: Bug? df uses f_bsize instead of f_frsize to calculate file system sizes
Date:
Thu, 10 May 2012 23:10:55 -0700
User-agent:
Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
On 05/10/2012 04:04 PM, Nikolaus Rath wrote:
But why isn't
it du using statvfs instead of statfs?
m4/fsusage.m4 says why:
Do not use statvfs on systems with GNU libc on Linux, because that function
stats all preceding entries in /proc/mounts, and that makes df hang if even
one of the corresponding file systems is hard-mounted, but not available.
statvfs in GNU libc on Hurd, BeOS, Haiku operates differently: it only makes
a system call.
I am not quite sure who's to blame here. This is a FUSE file system, and
there is only a callback handler for statvfs calls (but not statfs).
Should the FUSE kernel module maybe return st_frsize as st_bsize when
processing a statfs syscall?