One more thing to keep in mind, and this may have been mentioned before... depending on how you are invoking du you may be missing files or directories due to shell globbing. For example, if you are running du (or any command for that matter) from bash as it comes on most systems like this

du -s *

to obtain summary disk usage for everything, I would expect that it won't scan anything with a name beginning with a period '.' This is due to the fact that bash expands * to pretty much everything, except names starting with a period.

To test this, try

ls *

in a location where you have some files or directories with names beginning with a period, and you may find that they won't be listed. This behaviour of bash is configurable by setting the shell option "dotglob" by executing this:

shopt -s dotglob

which will make bash expand * to everything, also including names starting with a period. You can check the shell options with just

shopt

I am not sure whether this is what's missing in your case, Bevan, but it is one possible way of missing files and directories.

If you are using some other shell, this may all be different, but the key point is that shells may perform some kind of name expansion, and this is often different from what you would expect if you are thinking along the lines of regular expressions.

Kind regards,

Helmut.

--
+------------------------+
| Helmut Walle           |
| [email protected] |
| +64-3-388 39 54        |
+------------------------+

On Tue, 15 May 2012, Nick Rout wrote:

On Tue, May 15, 2012 at 12:01 PM, Nick Rout <[email protected]> wrote:
On Tue, May 15, 2012 at 10:59 AM, Bevan <[email protected]> wrote:
but cant find any other source that would fill up the root drive. note my
home parition is a separate partition and i have three ntfs partitions (
which i am attempting to condense and move over to ext4 partition

Well you need to find which file(s) are growing.

cd /
sudo du --max-depth=1 -x

Run it once, wait a while and run it again. Compare. The directory
which is filling up will be obvious. cd to it and run that command
again. rinse and repeat.

Then go that directory

oops that last line shouldn't be there. By the way the -x excludes
other file systems, so your /home and /proc and /sys should not be
scanned.
_______________________________________________
Linux-users mailing list
[email protected]
http://lists.canterbury.ac.nz/mailman/listinfo/linux-users

_______________________________________________
Linux-users mailing list
[email protected]
http://lists.canterbury.ac.nz/mailman/listinfo/linux-users

Reply via email to