On 05/11/2012 01:04 PM, Paul Eggert wrote: > On 05/11/2012 03:42 AM, Jim Meyering wrote: >> it's not clear that there is even a problem with our >> current use of statfs on glibc-based Linux systems. > > Yes, I find it curious. GNU/Linux statvfs > simply invokes statfs internally, right? > So why should it matter whether df uses statvfs > or statfs? And yet from Nikolaus Rath's evidence > it does appear that we have a problem with current FUSE systems. > > In the long run I'd rather have the Linux-based code > use statvfs, since that's the more-standard interface. > > Nikolaus, does the attached hack fix things for you? > Basically, it transforms a configure-time test into a > run-time test. After applying this patch, > you'll need to run autoreconf + configure before 'make'.
Yes, this works: With unpatched df: # df -h ~/tmp/mnt Filesystem Size Used Avail Use% Mounted on local:///home/nikratio/tmp/bucket 8.0G 240K 8.0G 1% /home/nikratio/tmp/mnt With patched df: # src/df -h ~/tmp/mnt Filesystem Size Used Avail Use% Mounted on local:///home/nikratio/tmp/bucket 1.0T 30M 1.0T 1% /home/nikratio/tmp/mnt Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
