/ 100% full - HELP !

[Steven E. Protter]

This thread is the be all and end all of finding junk in the root fileystem.

I've added it to favorites, and my vote is Bill Hassell gets a 10 point spot for his command which is great.

SEP

[GK_5]

Check for core dumps and delete/move from / file system
# find / -name "*core*" -print | pg

-GK-

[Todd McDaniel_1]

Havent seen this on the thread, but sometimes for tar devices folks may leave off the path and save it as cXtXdX

find . -name "cXtXdX" /

may show you a bad tarball...I know I have done that at least once...

[Michael Steele_2]

You spend a lot of time here.

[Tan Shirley]

Hi all,

Here's my du output.

#du -kx / |sort -rn |more
17093 /
14163 /sbin
3039 /sbin/fs
2752 /etc
1297 /sbin/fs/vxfs
1110 /sbin/fs/hfs
881 /etc/lvmconf
510 /sbin/lib
454 /etc/hpC2400
388 /sbin/fs/nfs
337 /etc/X11
269 /sbin/init.d
244 /etc/UPS.d
132 /sbin/fs/cdfs
122 /sbin/set_parms.d
121 /.elm
114 /etc/vue
112 /sbin/fs/lofs
98 /etc/opt
94 /etc/rc.config.d
94 /etc/mail

I still could not figure out what has gone wrong. And the worst thing is, I'm not able go into single-user mode as this is a live production 24x7 server. I'm still kind of puzzled why bdf shows 85MB and du shows around 30MB ?

#bdf /
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 86016 85104 888 99% /


Very interesting...

Anyone is able to solve this puzzle ?
I promise I will award points later.

[aparna challagulla]

hi Shirley,
can u post the o/p of
find / exec ll {} \; | grep ' -'
aparna

[Michael Steele_2]

You probably should start reading the responses posted above, for you've already been given the solution.

[aparna challagulla]

hi michael,
i am sorry. but i did read the responses :(.
i may have missed it as there are a lot of reponses.
aparna

[Steven E. Protter]

Tan Shirley,

I have looked at your output and believe you may have been a victim of the hidden file trick. Please see my earlier response.

At some point, please don't forget to assign points to those that helped you. There is a solution in this thread, its going to take some time to get to it, but this is a serious issue that didn't happen in five minutes. Probably.

I will say this: I used Bill Hassel's suggestion to figure out what was taking up 20% of the / filesystem on my production system.

SEP

[Yogeeraj_1]

hi,
*
I also think that Bill Hassel's suggestion is the way to go!
*
Sharing a similar experience of my mine!
*
- In single user mode, created directory /users and copied 50 MB of files
*
- In multi-user mode, i had a filesystem mounted on /users (size 800 MB)
*
- The 50 MB is hidden in the multi-user environment
*
two ways to get it back:
a. Umount all file systems and check /
(du -sk *)
b. Go to single-user mode and "du -sk *".
*
Hope this helps too!
*
Regards
Yogeeraj