:: This really sounds like a suggestion I saw earlier, in that you are
:: hiding the file with a mount.
::
:: Look at /etc/fstab.
:: Drop to runlevel 1.
:: Start unmounting filesystems. Do a "ls" on the mount point after
:: you have unmounted the filesystem. If it is not empty, you have
:: found your missing space.
Mark, although this was not in my head when I wrote you last evening,
I think Tom is onto your problem. In fact there is no
other explanation that I can see apart from a big bug
in reiserfs itself. I had suggested you drop to init 1
and umount everything but /usr (so that you could continue to use
`du'. I have this sneaking suspicion that the missing space may
by "underneath" /usr itself. I.e. in the directory onto
which the /usr partition is mounted. So from run level 1 unmount
/usr/ itself and see if the directory is empty.
You may get a "device busy" message in which case something at run
level 1 is still using /usr. In this case try booting "linux single"
That is, at the lilo prompt (if you use lilo in "prompt" mode)
just type
linux single
where you shd. substitute for "linux" whatever your
particular boot label is.
This shd. come up with only / mounted so that you can look in /usr.
You won't be able to use `du' as it is dynamically linked and requires
the libraries in /usr (and, itself, lives in /usr/bin I believe). You
could try compiling a version that is statically linked and put that
in /bin, but I'd first just look in the unmounted /usr and see if
it's empty.
Dean
