I have seen this symtom before on Suns but I ran into this a lot on AIX. One of the things to check is the open files and consider what has been cleaned up. Sometimes, if an open file is emptied or unlinked from the directory tree the disk space is not deallocated until the owning process has been terminated or restarted. The result is an unexplainable loss of diskspace. If this is the cause a reboot would clear it up. If you can't reboot consider any process the would be logging to that partition as a suspect and check all of your logs for any entries that imply rapid errors in a process.<br>
<br>
Another possibility is that the space has been used in an area that is now covered by a mounted filesystem. It is not uncommon if your system has failed boot at some point and entered system management mode, during which time in efforts to correct the problem moved or wrote something into one of the directories that are overlaid later, thinking that the filesystems were mounted. This has caused me a late night before. <br>
<br>
I guess the proper sequence would be looking at killable/restartable processes that do logging, then go for the reboot if possible and preferably boot to single user mode or better yet init state 1. This will give you the chance to verify the reduction in disk space. If it is still full, then look around in the directories that will be hidden by mounted filesystems in higher init states. That is probably the scenario that I would follow...<br>
<br>
Good luck, if it turns out to be some strange and exotic problem please post your solution.<br>
<br>
Thanks,<br>
Murray Chase