SCO

I am presuming that the purpose for the original question is disk space management.
"dfspace" or "df -v" are very accurate in terms of disk space available. If you run out of disk space on a file system and then delete a file, "df" correctly reports the new space.
I use "du -a |sort -r -n" to find where the space is being used. The output shows files in descending order by size, and directories in descending order by size of files within. Generally the problems show on the first page of output (either one or two extremely large files, or a directory with a large number of small files.)

But note that du, at least on SCO as you demonstrated, has the odd behavior to account space used on non disk based file system entities.
Edit: Solaris is actually doing the same, one more reason to avoid investigating non disk based file systems.

In any case, for a meaningful comparison, you should always use the -xoption to limit du to the requested file system.

OK. I was missing this point of using -x option with du. This helped me . Your posts helped me with that. But , do "df -k -v" also shows other fileystems mounted on / as well (it shows /stand separately) and if yes do this have any option like x for du, to limit it to / only.

If "Df -k -v" donot show other mounted filesystems , is it correct to take blocks as the whole partition size of / (excluding other filesystems)

Code:

# df -k -v
Mount Dir  Filesystem              blocks      used      free   %used
/          /dev/root            871678974  64246922 807432052     8%
/stand     /dev/boot                40959      6413     34546    16%

---------------
Dexter

df -k / will only show statistics belonging to the / file system. Mounted file systems information is never merged by df.
The -v option is useless with df.

"The -v option is useless with df."

-v option for displaying the used blocks which by default don't show up in df.
-------------------------

Lastly,Will it be correct to say from the following , that :

# du -xk / | tail -1
38195512

# df -k -v
Mount Dir Filesystem blocks used free %used
/ /dev/root 871678974 64231830 807447144 8%
/stand /dev/boot 40959 6413 34546 16%

For my / partition

total partition space (df)= 871678974 blocks = 871.6 gb (approx.)

present used space by whole partition (df -v) = 64231830 blocks= 64.2 gb (approx.)

space usage by files and directories (du) = 38195512 blocks = 38.1 gb (approx.)

space used by filesystem entities/data = 64.2 - 38.1 gb = 26.1 gb (approx.)

-------------

regards,

Dexter

For comparison:

Code:

#dfspace
/z        : Disk space: 354341.99 MB of 357144.24 MB available (99.22%).
                                                         
 
# cd /z                                                                 
# l                                                                     
total 0                                                                 
drwxr-xr-x    2 root     sys         96 Aug 22 20:47 lost+found

I think that what has made the 26gb of overhead appear excessive is the fact that the partition is only eight percent used.
So 26gb over 64gb used looks unusual, whereas 26gb/871gb total is only three percent waste.

I'm not familiar enough with SCO but I guess it support more than one file system type so are you using the same one, and which one is it ?

@dextergenious: you are right with the -v option. As it is not POSIX, it has been dropped in other Unix implementations.

You states "space used by filesystem entities = 26.1 gb". Did you reboot and you perform a fsck to rule out deleted still open files and file system corruption ?