Type "df -k" and look at the result. Removing files in other filesystems won't help if / is full. You've got to remove stuff in the root filesystem. Note that /proc is a separate filesystem. That right there should tell you that looking at /proc is barking up the wrong tree. What's worse is trhat /proc consumes no disk space at all. It's a psuedo filesystem. Psuedo means make-believe. So ignore /proc and the other filesystems...if root is full, you've got to address that by looking at root.
If root has filled it's because someone wrote some files there. So a reasonable approach is to look at a recently written files in root...
find / -mount -mtime -10 -type f -print | xargs ls -l
The -mtime -10 says written to less than 10 days ago. You may need to adjust that.
Kelam,
I found out the reason, under /dev one link was created like (rmt0 -> /dev/rmt/....) which was not a right link & i removed that,
i don't know how it had been created cause the client are not familliar to run any unix command.
One more thing was .CPR which had very large size, i executed
cat /dev/null >.CPR to make its size zero.
now / is ok.
Yes, I think since /proc is a pseudo, it's always 100%. Also, core dumps are occasionally dumped to / . They can be very large. Depending on your distro, you can select a different filesystem to write core dumps, automatically delete them, or set conditional space rules.