Hi,
Here's a case where GNU df 5.2.1 displays figures that are totally off
the reality.
[EMAIL PROTECTED]:/smb/ibook/data/temp $ df --version
df (coreutils) 5.2.1
...
[EMAIL PROTECTED]:/smb/ibook/data/temp $ df .
Filesystem 1K-blocks Used Available Use% Mounted on
//ibook/bruno
On Tue, 16 Aug 2005, Bruno Haible wrote:
[EMAIL PROTECTED]:~ $ ls -ld data
lrwxr-xr-x 1 bruno bruno 17 24 Aug 2004 data - /Volumes/UserData
[EMAIL PROTECTED]:/smb/ibook $ ls -ld data
drwxr-xr-x1 brunouser 4096 Aug 11 00:54 data
The mistake that 'df' did is: When it climbed
Bob,
Sorry it took me so long to get back to you, but I have a few answers to
your questions. Here's the output from the commands you asked me to
run...
[root wesdintel28 root]# id
uid=0(root) gid=0(root) groups=0(root)
[root wesdintel28 root]# id -Gn -- root
root mqm mqbrkrs
[root
Bruno Haible [EMAIL PROTECTED] writes:
The mistake that 'df' did is: When it climbed up directories until it
found a mount point
/smb/ibook/data/temp
/smb/ibook/data
/smb/ibook
it only considered mount points on the current host (linuix), but ignored
mount points and symbolic links
Philip Rowlands [EMAIL PROTECTED] writes:
(Open question) Should the reported free space be the combination of
both/all server partitions, and how should df discover them?
There is nothing that can be fixed in user space. It can only report as
much as the kernel is revealing to it. And the
