65644 – df (sys-apps/coreutils) improperly handles filesystems greater than 4TB

I first noticed this almost a year ago but I forgot to report it.  With Linux 2.6/amd64 it is now possible to create filesystems greater then 2/4TB.  It turns out that df rolls over the size of the displayed filesystem after 4TB.

This is how a 4.5TB filesystem with ~400GB of data on it is displayed with sys-apps/coreutils-5.2.0-r2.

nkfb0 root # df -k
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda3             15757280   6248088   8708756  42% /
/dev/root_volume/home
                     210399784  13499740 194779340   7% /home/nkfb0
none                   2008512         0   2008512   0% /dev/shm
/dev/sda1               101108     10824     85068  12% /boot
/dev/archive/scr0    585999328 401958244 178169060  70% /scr0
nkfb0 root # df -H
Filesystem             Size   Used  Avail Use% Mounted on
/dev/sda3               17G   6.4G   9.0G  42% /
/dev/root_volume/home
                       216G    14G   200G   7% /home/nkfb0
none                   2.1G      0   2.1G   0% /dev/shm
/dev/sda1              104M    12M    88M  12% /boot
/dev/archive/scr0      601G   412G   183G  70% /scr0
nkfb0 root # lvdisplay
  --- Logical volume ---
  LV Name                /dev/archive/scr0
  VG Name                archive
  LV UUID                TyyfxB-dQZP-iFSR-iPjn-RRz3-Q4tu-mV2Vdp
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                4.55 TB
  Current LE             4656
  Segments               1
  Allocation             next free (default)
  Read ahead sectors     0
  Block device           253:1

  --- Logical volume ---
  LV Name                /dev/root_volume/home
  VG Name                root_volume
  LV UUID                xInYjE-hEFg-xGHO-ldAT-CS41-j3r4-gKl1lh
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                202.25 GB
  Current LE             51775
  Segments               1
  Allocation             next free (default)
  Read ahead sectors     0
  Block device           253:0

I'd guess that a 32bit unsigned int is overflowing but I haven't looked at the source.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Portage 2.0.50-r6 (default-amd64-2004.0, gcc-3.3.3, glibc-2.3.3_pre20040420-r0,
2.6.5-gentoo-r1)
=================================================================
System uname: 2.6.5-gentoo-r1 x86_64 5
Gentoo Base System version 1.4.12
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CFLAGS="-O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref
/usr/share/config /usr/share/texmf/dvipdfm/config/
/usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/
/usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://gentoo.mirrors.pair.com/ ftp://gentoo.mirrors.pair.com/
ftp://ibiblio.org/pub/Linux/distributions/gentoo/"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X amd64 apm arts avi berkdb cdr crypt encode esd foomaticdb gdbm gif gnome
gnome2 gpm gtk gtk2 imlib jpeg kde libg++ libwww mikmod motif mozilla mpeg
multilib mysql ncurses nls nogcj nptl oggvorbis opengl oss pam pdflib perl png
python qt quicktime readline sdl slang spell ssl tcltk tcpd tetex truetype xml2
xmms xv zlib"