Colin, On Sunday 14 November 2004 05:10, Colin Murphy wrote:
On Sunday 14 November 2004 12:05, S. Bulterman wrote:
This works only for mounted filesystems. So was data1 mounted??
Yes, I think so. With things like automount it is sometimes hard to be certain, so I went and did:-
colin@linux:/data1> touch /data1/emptytestfile colin@linux:/data1> ls emptytestfile colin@linux:/data1> du -h --max-depth=1 0 . colin@linux:/data1> df /data1 Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda2 10490104 7525288 2964816 72% / colin@linux:/data1>
For the record Konqueror now shows the file but still shows that something else has taken 7.2GB of the space in this partition.
No, I don't think it does. That "df" output means that nothing is mounted on "/data1". Df accepts files and directories as arguments and then reports on the file system that holds those files or directories. The output it's producing for you implies there's nothing mounted on /data1. You can see what's mounted by using the "mount" command or by viewing "/proc/mounts". Naturally, coming directly from the kernel, /proc/mounts is not subject to any potential discrepancy as the contents of "/etc/mtab" can be. If you haven't already, read the man pages on "du" and "find" (it has options to find files using their size or size range as a criterion) to help you resolve this problem. If you end up with a very large list (say of directories and their space occupancy from du), use "sort -rn" to find the largest ones. And if the list you need to sort doesn't have the sizes first, read about sort's key field selection options. You may find the "-S" / "--separate-dirs" option to du helpful; it keeps du from adding the contents of subdirectories into the size it reports for directories higher up in the file system. Good luck.
-- Colin@SpudULike.me.uk As seasons go I especially like pepper.
That's "seasonings"... Randall Schulz