This not a bug but rather an inconsistent output between these two du options,
which is not documented in the manpages.
Suppose 'somefile' is a file containing a lot of zeros.
Then I get:
$ du -k somefile
12
$ du somefile
12
$ du -b somefile
4194432
It seems that du -b is returning the size of the file, and not the "disk
usage" of that file.
(Using coreutils-5.94, linux on both reiserfs and ext3)
Miguel Barão