topic 100% FULL in Operating System - HP-UX

100% FULL

Cat_4 — Fri, 03 Oct 2003 02:04:16 GMT

Dear all,

On 9/29, Shirley Tan has raised her problem of 100% full under /. Lots of you share the valuable sys command. Shirley, can you finally solve the problem ?

Actually, I have the similar problem with her:
Here is my du report :

# du -kx / | sort -rn

40418 /

21065 /etc

18847 /sbin

9671 /etc/lvmconf

9454 /etc/opt

5485 /etc/opt/resmon

3684 /sbin/fs

3511 /etc/opt/resmon/log

2248 /etc/opt/samba

2242 /etc/opt/samba/codepages

1657 /sbin/fs/vxfs

1550 /sbin/fs/hfs

1453 /etc/opt/cifsclient

1423 /etc/opt/cifsclient/unitables

955 /etc/opt/resmon/lbin

935 /etc/opt/resmon/lib

512 /sbin/lib

490 /etc/X11

447 /etc/hpC2400

402 /sbin/init.d

303 /.netscape

224 /sbin/fs/cdfs

192 /etc/mail

157 /etc/opt/omni

148 /sbin/fs/lofs

106 /etc/opt/dce

105 /sbin/set_parms.d

99 /etc/rc.config.d

95 /etc/ppp

80 /etc/vue

77 /etc/opt/resmon/lib/nls/msg/C

77 /etc/opt/resmon/lib/nls/msg

77 /etc/opt/resmon/lib/nls

68 /sbin/fs/nfs

67 /.dt

63 /etc/SnmpAgent.d

49 /etc/vue/config

49 /etc/sam

47 /.sw

46 /.sw/sessions

43 /etc/opt/resmon/persistence

42 /etc/ppp/Examples

39 /etc/opt/omni/options

38 /.dt/help

36 /sbin/fs/autofs

36 /etc/opt/resmon/dictionary

34 /etc/opt/omni/dltemplates

31 /etc/vue/icons

30 /sbin/lib/eisa

25 /etc/vue/config/types

25 /etc/opt/omni/dltemplates/lists

24 /etc/uucp

23 /etc/opt/omni/datalists

22 /etc/vue/config/dialogs

19 /.dt/sessions

19 /.dt/help/root-dw-1

19 /.dt/help/root-192.168.68.66-0

17 /dev

16 /.netscape/cache

15 /etc/vue/icons/Color

14 /etc/patrol.d

14 /etc/opt/omni/devices

12 /etc/opt/omni/cell

11 /etc/opt/omni/dltemplates/lists/sap

10 /.vnc

9 /etc/opt/resmon/lib/krm

9 /etc/opt/omni/dltemplates/schedules

8 /etc/patrol.d/security_policy

8 /etc/opt/omni/schedules

8 /etc/opt/omni/dltemplates/schedules/datalist

8 /etc/opt/omni/dltemplates/lists/datalist

8 /etc/dt

8 /.dt/sessions/current.old

8 /.dt/sessions/current

7 /etc/vue/config/types/tools

6 /etc/opt/omni/sg

6 /etc/opt/omni/customize

6 /etc/net

6 /etc/hparray

6 /etc/dt/config

5 /etc/vue/config/types/marketplace

5 /etc/opt/omni/dsi

5 /etc/opt/omni/dltemplates/lists/oracle8

4 /sbin/lib/mfsconfig.d

4 /etc/vue/icons/Vuewm

4 /etc/vue/config/types/tools/Performance

4 /etc/skel

3 /sbin/rc2.d

3 /etc/vue/config/types/tools/System_Info

3 /etc/vue/config/types/marketplace/Demos

3 /etc/opt/ignite

3 /etc/X11/C/print/attributes

3 /etc/X11/C/print

3 /etc/X11/C

3 /.dt/sessionlogs

2 /sbin/rc3.d

2 /sbin/rc1.d

2 /etc/vue/config/types/marketplace/Ordering_Info

2 /etc/vue/config/Xsession.d

2 /etc/opt/resmon/monitors

2 /etc/opt/omni/users

2 /etc/opt/cifsclient/pam

2 /etc/net/ticotsord

2 /etc/net/ticots

2 /etc/net/ticlts

2 /etc/local

2 /etc/dt/appconfig

2 /etc/default

2 /etc/X11/lbxproxy

2 /dev/ptym

2 /dev/pty

2 /dev/pts

1 /sbin/rc0.d

1 /sbin/SnmpAgtStart.d

1 /export/shared_roots/OS_700/var/adm/sw

1 /export/shared_roots/OS_700/var/adm

1 /export/shared_roots/OS_700/var

1 /export/shared_roots/OS_700

1 /export/shared_roots

1 /export

1 /etc/vhelp/volumes/C

1 /etc/vhelp/volumes

1 /etc/vhelp

1 /etc/sam/custom

1 /etc/opt/resmon/pipe

1 /etc/opt/omni/snmp

1 /etc/opt/omni/dlgroups

1 /etc/opt/omni/barschedules

1 /etc/opt/omni/barlists

1 /etc/opt/OV/share/registration/C/perf

1 /etc/opt/OV/share/registration/C

1 /etc/opt/OV/share/registration

1 /etc/opt/OV/share

1 /etc/opt/OV

1 /etc/lp

1 /etc/eisa

1 /etc/dt/config/Xsession.d

1 /etc/dt/appconfig/types

1 /etc/dt/appconfig/appmanager

1 /etc/ddfa

1 /etc/acct

1 /etc/X11/proxymngr

1 /etc/X11/fs

1 /dev/vg02

1 /dev/vg01

1 /dev/vg00

1 /dev/rmt

1 /dev/rdsk

1 /dev/dsk

1 /dev/diag

1 /.netscape/xover-cache/host-news

1 /.netscape/xover-cache

0 /vtc_u03

0 /vtc_u02

0 /tmp_mnt

0 /sbin/rc4.d

0 /sbin/fs/cifs

0 /nsmail

0 /lost+found

0 /etc/vhelp/families/C

0 /etc/vhelp/families

0 /etc/switch

0 /etc/patrol.d/security_policy/bak

0 /etc/patrol.d/bak

0 /etc/opt/resmon/lock

0 /etc/opt/omni/rptschedules

0 /etc/opt/omni/rptgroups

0 /etc/opt/omni/rid

0 /etc/opt/omni/mom/cell_info

0 /etc/opt/omni/mom

0 /etc/opt/omni/dltemplates/schedules/sybase

0 /etc/opt/omni/dltemplates/schedules/stream

0 /etc/opt/omni/dltemplates/schedules/sap

0 /etc/opt/omni/dltemplates/schedules/oracle8

0 /etc/opt/omni/dltemplates/schedules/oracle/rcs

0 /etc/opt/omni/dltemplates/schedules/oracle/ccs

0 /etc/opt/omni/dltemplates/schedules/oracle/bcs

0 /etc/opt/omni/dltemplates/schedules/oracle

0 /etc/opt/omni/dltemplates/schedules/mssql

0 /etc/opt/omni/dltemplates/schedules/msexchange

0 /etc/opt/omni/dltemplates/schedules/informix

0 /etc/opt/omni/dltemplates/schedules/enabler

0 /etc/opt/omni/dltemplates/lists/sybase

0 /etc/opt/omni/dltemplates/lists/stream

0 /etc/opt/omni/dltemplates/lists/oracle/rcs

0 /etc/opt/omni/dltemplates/lists/oracle/ccs

0 /etc/opt/omni/dltemplates/lists/oracle/bcs

0 /etc/opt/omni/dltemplates/lists/oracle

0 /etc/opt/omni/dltemplates/lists/mssql

0 /etc/opt/omni/dltemplates/lists/msexchange

0 /etc/opt/omni/dltemplates/lists/informix

0 /etc/opt/omni/dltemplates/lists/enabler

0 /etc/opt/omni/barschedules/sybase

0 /etc/opt/omni/barschedules/stream

0 /etc/opt/omni/barschedules/sap

0 /etc/opt/omni/barschedules/oracle8

0 /etc/opt/omni/barschedules/oracle

0 /etc/opt/omni/barschedules/mssql

0 /etc/opt/omni/barschedules/msexchange

0 /etc/opt/omni/barschedules/informix

0 /etc/opt/omni/barschedules/enabler

0 /etc/opt/omni/barlists/sybase

0 /etc/opt/omni/barlists/stream

0 /etc/opt/omni/barlists/sap

0 /etc/opt/omni/barlists/oracle8

0 /etc/opt/omni/barlists/oracle/rcs

0 /etc/opt/omni/barlists/oracle/ccs

0 /etc/opt/omni/barlists/oracle/bcs

0 /etc/opt/omni/barlists/oracle

0 /etc/opt/omni/barlists/mssql

0 /etc/opt/omni/barlists/msexchange

0 /etc/opt/omni/barlists/informix

0 /etc/opt/omni/barlists/enabler

0 /etc/opt/omni/CDROM/drivers

0 /etc/opt/omni/CDROM

0 /etc/opt/dce/zoneinfo

0 /etc/opt/dce/security

0 /etc/opt/audio

0 /etc/lp/sinterface

0 /etc/lp/member

0 /etc/lp/interface

0 /etc/lp/info

0 /etc/lp/class

0 /etc/lp/cinterface

0 /etc/ftpd/pids

0 /etc/ftpd/ftp-exec

0 /etc/ftpd

0 /etc/dt/config/C

0 /etc/dt/appconfig/types/zh_TW.eucTW

0 /etc/dt/appconfig/types/zh_TW.big5

0 /etc/dt/appconfig/types/zh_CN.hp15CN

0 /etc/dt/appconfig/types/sv_SE.iso88591

0 /etc/dt/appconfig/types/ko_KR.eucKR

0 /etc/dt/appconfig/types/ja_JP.eucJP

0 /etc/dt/appconfig/types/ja_JP.SJIS

0 /etc/dt/appconfig/types/it_IT.iso88591

0 /etc/dt/appconfig/types/fr_FR.iso88591

0 /etc/dt/appconfig/types/fr_CA.iso88591

0 /etc/dt/appconfig/types/es_ES.iso88591

0 /etc/dt/appconfig/types/de_DE.iso88591

0 /etc/dt/appconfig/types/C

0 /etc/dt/appconfig/icons/C

0 /etc/dt/appconfig/icons

0 /etc/dt/appconfig/help/C

0 /etc/dt/appconfig/help

0 /etc/dt/appconfig/appmanager/zh_TW.eucTW

0 /etc/dt/appconfig/appmanager/zh_TW.big5

0 /etc/dt/appconfig/appmanager/zh_CN.hp15CN

0 /etc/dt/appconfig/appmanager/sv_SE.iso88591

0 /etc/dt/appconfig/appmanager/ko_KR.eucKR

0 /etc/dt/appconfig/appmanager/ja_JP.eucJP

0 /etc/dt/appconfig/appmanager/ja_JP.SJIS

0 /etc/dt/appconfig/appmanager/it_IT.iso88591

0 /etc/dt/appconfig/appmanager/fr_FR.iso88591

0 /etc/dt/appconfig/appmanager/fr_CA.iso88591

0 /etc/dt/appconfig/appmanager/es_ES.iso88591

0 /etc/dt/appconfig/appmanager/de_DE.iso88591

0 /etc/dt/appconfig/appmanager/C

0 /etc/bgs/PERL

0 /etc/bgs/ARM

0 /etc/bgs

0 /etc/X11/C.iso88591

0 /dev/telnet

0 /dev/screen

0 /dev/rscsi

0 /dev/rac

0 /dev/krm

0 /dev/diag/rmt

0 /dev/ac

0 /cdrom

0 /SD_CDROM

0 /.netscape/archive

0 /.dt/types/fp_dynamic

0 /.dt/types

0 /.dt/tmp

0 /.dt/sessions/system

0 /.dt/palettes

0 /.dt/icons

0 /.dt/appmanager

0 /.dt/Trash

0 /.dt/Desktop

it use around 130MByte of my disk space. The bdf extract is as follow :

/dev/vg00/lvol3 204800 202585 2136 99%
It use around 200Mbyte.

Here is my question :

1. why i have such a lot of zero byte directories ? Would the zero byte directories use up my disk space ?

2. Can I delete them ? Or which I should not deleted ?

3. it shows me that around 200M has been used but du report shows I am 129M used up.Do you think I fall into the same situation with Shirley ?

4. Can I do the lvextend so that I could have more disk space for the root ? What is the step for that ?

Thanks for you help in advance and I promise I will grant point for to all of you.

Many many thanks!

Cat

Re: 100% FULL

Stanimir — Fri, 03 Oct 2003 02:16:47 GMT

Hi!
First of all you could initialize log-files:
Look at:
"3511 /etc/opt/resmon/log"

But dont simply remove it, use command:

# > logfile.log

and remove 0-size dirs also, using: rm -r.

Regards.

Re: 100% FULL

john korterman — Fri, 03 Oct 2003 02:34:28 GMT

Hi,
do not remove any zero size directories!
more details later...
regards,
John K.

Re: 100% FULL

Bhuvaneswari Selvaraj — Fri, 03 Oct 2003 02:34:41 GMT

Hi,

1. Zero byte directories - most of them are created when u install a product or OS. They are like place holders which may get populated during the course of system use. Few others are lock files, which even they r zero, their existence really matters.

2. It is not advisable to remove them.

3. du shows the data in multiples of 512/1024 and hence it is not pretty accurate. always better to rely on bdf for disk usage.

4. lvextend can be used provided that you have Mirrored Disk software.. I dont have any idea about this, sorry.

Re: 100% FULL

john korterman — Fri, 03 Oct 2003 02:43:30 GMT

Hi again,
try first to clean up using SAM:
SAM-->Routine Tasks-->System Log Files-->

and look for files >100% of the recommended size. Select them for trimming to the recommeneded size (ascii files) or to zero (non-ascii).

Btw: directories created with the default size are smaller than 1 block, that is why they appear as szie zero, which they are not.

regards,
John K.

Re: 100% FULL

john korterman — Fri, 03 Oct 2003 02:54:42 GMT

Hi again,
forgot to mention that you can issue the commmand "cleanup", which clears space by removing superfluous patches.

regards,
John K.

Re: 100% FULL

Pete Randall — Fri, 03 Oct 2003 05:23:07 GMT

Cat,

First off, could you post a new du command output, please? Yours is so cluttered it's hard to read. Try running "du -sk /* |sort -n" and post those results.

It looks to me like most of your space is used up in the /etc directory, particulary /etc/resmon/log, /etc/opt, /etc/lvmconf. The resmon/logs can probably be cleaned out. /etc/opt should be looked into, there's way too much space used there. Sam for /etc/lvmconf.

Pete

Re: 100% FULL

Bruno Ganino — Fri, 03 Oct 2003 06:35:49 GMT

Cat, the Number 0 that you see indicates that the size does not exceed 1 block (generally 512 byte) therefore is not correspondent to 0 byte. Regard to the removal of these dir, I would not make it
because is much dangerous (excpecially the remove manual with command rm).
Leaves all as it is, but If you want to cancel something, uses SAM like already said.
Bye
Bruno

Re: 100% FULL

Steven E. Protter — Fri, 03 Oct 2003 06:56:31 GMT

You probably have some big files in the top of root / and/or /etc/

Also, don't forget about the old hidden file trick.

Any file written to a folder prior to mounting a filesystem on it will be invisible but still take up space.

When all other measures fail, consider booting the system into single user mode.

Interupt the boot at the console at the 10 second prompt

bo

Y Interact

hpux -is

Baes on your report, I think you may have hidden files.

You really don't need this thread. More than likely your problem is different from Shirley's. You can just read that thread and follow the suggestions there.

Nobody is going to find the file for you. Eventually you are going to have to slowly look for stuff that doesn't belong. If you lack confidence, post some updates asking about specific files.

Good Luck,

SEP

Re: 100% FULL

Marco Santerre — Fri, 03 Oct 2003 07:04:42 GMT

Because everyone have already answered most of your questions, I'll just go to #4 right away.

Because you need to have contiguous space for /, it may well be that you won't be able to use lvextend to extend / unless you have a bigger disk, so the only option for you to extend / filesystem would either to re-install HP-UX with a bigger / filesystem, or (best option) do a make_tape_recovery and interrupt the process to increase the size of / file system.

Re: 100% FULL

Kent Ostby — Fri, 03 Oct 2003 07:18:14 GMT

Cat -- I'm not sure what Shirley's problem was.

I think your problem might be in a couple of areas .

#1) You may have some "hidden" files which are underneath mount points.

#2) You may have some large files in / that you can move elsewhere.

To tackle #1 you have to reboot into single user mode and do ls -l commands on your mountpoints. There may be something in /var or /tmp but under the mounted filesystem .

To tackle #2 of course you just need to take a look and see whats there.

Finally, as always, you can do:

find / -size +1000000c -print

Best regards,

Kent M. Ostby

Re: 100% FULL

Michael Steele_2 — Fri, 03 Oct 2003 07:18:23 GMT

Can you attach:

- quot /

- find /dev -type f

All I can see is /etc/opt/resmon/log as pointed out above.

1) These are all system files that I can see.

2) zero byte directories only use up inodes. Don't use this as a criteria for removing files in /.

3) You may have a runaway process holding onto disk space. In this case, only a reboot will get rid of it.

4) No. First three logical volumes in vg00 are contiguous and can't be extended except through re-installation. Easiest re-installation is with a ignite make_tape_recovery install.

Re: 100% FULL

Bruno Ganino — Fri, 03 Oct 2003 09:12:22 GMT

Cat,
Search the temporary-files, lock-files, log-files, history-files, crono-files, printerspool-files. Use "find" command in path /etc and /var. I think that these files occupies much space. You cancel the unnecessary files.
Bruno