Paul E Condon wrote:
> On 20101223_002101, Bob Proulx wrote:
...
>> > > To see the values that the kernel is returning to df's statfs call
>> > > please run the following command and report the contents of the file.
>> > >
>> > > $ strace -v -e trace=statfs -o /tmp/df.strace.out df /dev/sde1
...
> Also, /tmp/df.strace.out is empty after running your suggested diagnostic.
> So is the above discussion an instance of sour grapes reasoning?
kernel differences? The above works fine for me with unstable's
2.6.32-5-amd64 and self-compiled df from coreutils-8.7.x:
This variant might be more useful:
$ strace -v -e file -o /tmp/df.strace.out df /dev/sde1
If it too leaves the output file empty, try this:
$ strace -o /tmp/df.strace.out df /dev/sde1
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
