94% usage of directory / in rp5470

[ajk_5]

Dear all,

I am just wondering why the / directory is 94% suddently. I can't find the reason. Any way I can reduce the size? Thanks.

Best Regards
Ajk

Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 204800 191664 13096 94% /
/dev/vg00/lvol1 298928 57504 211528 21% /stand
/dev/vg00/xpo 4194304 835637 3148811 21% /xpo
/dev/vg00/lvol8 4710400 363040 4313464 8% /var
/dev/vg00/lvol7 2621440 1469128 1143368 56% /usr
/dev/vg00/lvol4 204800 12064 191240 6% /tmp
/dev/vg00/lvol6 1245184 909888 332880 73% /opt
/dev/d2/livedb 2097152 46000 1924395 2% /livedb
/dev/d3/db4 17776640 4974968 12601708 28% /livedb/db4
/dev/d2/db3 17776640 5194700 12385412 30% /livedb/db3
/dev/d1/db2 13332480 561236 12372206 4% /livedb/db2
/dev/d1/db1 13332480 5531372 7557358 42% /livedb/db1
/dev/vg00/lvol5 1048576 598712 446624 57% /home
/dev/dskdump/dskdump
35557376 16925936 18489544 48% /dskdump
/dev/vg00/devlp 8388608 3806414 4439034 46% /devlp

[Zigor Buruaga]

Hi,

Look at "/dev/rmt", maybe you can find any incorrect ( and large ) file.

Use "du" command to search for big files into /

Kind regards,
Zigor

[Robert-Jan Goossens · Accepted solution]

Hi,

# cd /
# find . -size +10000 -xdev -exec ls -l {} \;
Look for any files that should not be in /

Hope it helps,

Robert-Jan.

[Chapaya]

Hello Ajk ,

I see that your / directory is a little small , i suggest you to increase this directory to 400M .
Do you have OnlineJFS ?
If no , you need to reboot your system and go to maintenance mode and then to increase your / .

Check home directory . may be one of your users cause this event .

Bye ,
Eran .

[T G Manikandan]

Just do a

#du -k|sort -nr|more

check for the huge size dir.

Also it could be like you have copied something into a non-mounted directory inside root.

Also check the /dev/rmt where there are files of huge size.

[Piergiacomo Perini]

Hi,

I use to check with this command:

cd /
du -x * | sort -rn | more

in order to have a "ranking" of file size
(obviously I exclude mount points).
So you can find some huge log file, core file, etc etc.

HiH

[Ken Burke]

If you do decide to increase the size of your / file system then the only supported method is to do some form of reinstall. Using Ignite/UX is the easiest way to do this.

Just extending the size of / will probably make your system unbootable and defiantly make it unsupported by HP.

That said around 200MB should be fine for the / file system, the methods listed above to look for large out of place files should solve your problem.

[Joaquin Gil de Vergara]

check size of files and directories that are not file systems!

for i in $(ls /)
do
for j in $(bdf | awk '{print $6}')
do
VAR=0
if [ '/'"$i" = "$j" ]
then
VAR=1
fi
done
if [ "$VAR" = 0 ]
then
du -sk '/'$i
fi
done

[Bill Hassell]

The two most common reasons for / to fill up are misspelled device files (especially tape devices) and install programs that refuse to follow industry standards for the application directory. In the first case, someone may have run tar or cpio or fbackup and specified /dev/rmt/om, not /dev/rmt/0m (spelling counts!) and the tape did not move. But the /dev directory is now VERY large. To check /dev, use this command:

find /dev -type f

There should be *NO* results as /dev contains only directories and device files, no regular files.

A large core dump from a program could cause this problem. Using the command:

du -kx / | sort -rn | head

will show the biggest directories. A typical / directory only uses between 60 and 120 megs.

In the second case, there may be some 'special' directory created by an install program. There should never be any applications stored in the / directory. All install programs should either:

1. put the app in /opt where it belongs, or

2. ask you where you would like the application to be stored.

[Keith Bevan_1]

Ajk,

In addition to all the good advice above, also check that you have all you filesystems mounted. (check /etc/fstab against your bdf list).

Previously I have seen systems with unmounted filesystems and users have run a restore or copied files onto a directory structure which is not mounted on a mount point. Consequently the files are located under the / filesystem.

Keith

[Kent Ostby]

The suggestions above are great. If for some reasons you still can't find it, it could be that a process is creating a large temporary file on your system somewhere that uses up disk space but wont show up via ll or du.

Usually if this is the case, it is a process that is chewing up a lot of cpu.

One quick and dirty way to check for these types of processes would be:

ps -ef | cut -c42-80 | sort -nr | head

Another caveat to what was listed above about making sure all of your filesystems are mounted is that if you had previously not had all of your filesystems mounted and created a large file under a mount point and now you have all of your file systems mounted, that huge file will be invisible to you.

As a last resort, if you can't find the large files, do a reboot and boot INTO single user mode with only / mounted and do an ll of all of your mountpoints to see if there are any files hidden there.

Best regards,

Kent M. Ostby