Spooky bad values from df

Caidence · 11-20-2003, 01:25 PM

df is returning really bad values. Here, I'll show you:

Code:

[tachycardic:caidence]$ df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/hda1            -2647926523368         1         0   9% /
/dev/hda2            -515486986193         1         0   1% /home
/dev/hdc1            -15106703008423         1         0  31% /var/ftp
[tachycardic:root]# df -m
Filesystem           1M-blocks      Used Available Use% Mounted on
/dev/hda1            -2585865745         1         0   9% /
/dev/hda2            -503405260         1         0   1% /home
/dev/hdc1            -14752639657         1         0  31% /var/ftp
[tachycardic:root]# df.giga
Filesystem           1G-blocks      Used Available Use% Mounted on
/dev/hda1             -2525260         1         0   9% /
/dev/hda2              -491607         1         0   1% /home
/dev/hdc1            -14406875         1         0  31% /var/ftp

I am running a very simple, new, linux box (Debian 3.0 Woody).
hda1 and hda2 are simply enough ext2,
and hdc1 is a brand spanking new ext3, but it just took a lot of activity.

Also, mind you, according to the system, hdc1 is full, not at 31%

Could this be ext3's doing? Any clue?

Thanks,
Caidence

meldroc · 11-20-2003, 05:48 PM

That's very strange. I'm thinking that maybe df is screwed up somehow, but I wouldn't bet my data on that.

You might want to drop to emergency mode (a variety of single-user mode where the partitions are mounted read-only - boot with params "linux emergency" in LILO or GRUB), then run fsck on each partition to fix any corruption.

Other than that, if you have a bootable Linux CD (the Woody install CD should be good enough for this, try booting that, getting to a shell, mounting your partitions, and see if df works correctly on that setup.

Just in case df is screwed, you might try reinstalling df (and the other core utilities) with apt-get install --reinstall coreutils.

Other than that, you have me stumped.

Shade · 11-21-2003, 01:57 AM

This can also happen if you chose a different inodes / blocks layout for your partitions.

Did you choose something other than default?

-Shade