HPUX root file system reaching 90%

[mollywilliams]

Hi,

I have HPUX 11i v2 with root filesystem is 85% used. I need to do housekeeping but do not have idea on what files can be deleted.

How can i extend root filesystems without distrubing existing OS in it?

This is my big directories that i can sort out:

# bdf /
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 4358144 3697272 655976 85% /
# du -kx / | sort -rn | head -20
3669416 /
3399632 /var
3041656 /var/adm
3001576 /var/adm/sw
2596168 /var/adm/sw/save
257440 /var/adm/sw/save_custom
256824 /var/adm/sw/save/PHCO_39220
255856 /var/adm/sw/save/PHCO_33081/VEA-FILESET/opt/VRTSob
255856 /var/adm/sw/save/PHCO_33081/VEA-FILESET/opt
255856 /var/adm/sw/save/PHCO_33081/VEA-FILESET
255856 /var/adm/sw/save/PHCO_33081
253864 /var/adm/sw/save/PHCO_35890
231048 /var/opt
215136 /var/adm/sw/save/PHCO_39220/VXVM-RUN
212184 /var/adm/sw/save/PHCO_35890/VXVM-RUN
203496 /var/adm/sw/save/PHSS_35055
200112 /var/adm/sw/save_custom/PHCO_36028
145776 /var/adm/sw/products
141672 /etc
136584 /var/adm/sw/save/PHCO_31555
#

Thanks in advance,
molly williams.

[Dennis Handly]

You should have /var under a different filesystem than /.

For /var/adm/sw/save/ you can use cleanup(1m) to commit patches.  See the following tag:

http://community.hpe.com/t5/tag/cleanup/tg-p/category-id/itrc-117

http://community.hpe.com/t5/System-Administration/how-to-use-the-clean-up-command/m-p/6689532

http://community.hpe.com/t5/System-Administration/var-more-then-90-full/m-p/6134019#M484750

http://community.hpe.com/t5/System-Administration/Is-it-safe-to-remove-patches-in-var-adm-save-if-is-how/m-p/3404284

http://community.hpe.com/t5/System-Administration/var-Issue/m-p/5441761#M477701

[mollywilliams]

Hi Dennis,

Below are my output ofcleanup -p -c 2:

# cleanup -p -c 3

### Cleanup program started at 11/22/33  15:13:06

Preview mode enabled. No modifications will be made.

Commit patches superseded at least 3 time(s) on 's28bf246'.

Obtaining superseded patch information...done.

No non-committed patches superseded at least 3 time(s) are present.

All information has been logged to /var/adm/cleanup.log.

### Cleanup program completed at 11/22/33  15:13:06

# cleanup -p -c 2

### Cleanup program started at 11/22/33  15:13:22

Preview mode enabled. No modifications will be made.

Commit patches superseded at least 2 time(s) on 's28bf246'.

Obtaining superseded patch information...done.

The following patches superseded at least 2 time(s) can be committed:

Superseded  # Times Superseded  Disk Space in /var/adm/sw/save  Superseded By

==========  ==================  ==============================  =============

PHCO_31590           2                     8192 bytes             PHCO_36742

PHCO_34974           2                 11018240 bytes             PHCO_36563

All information has been logged to /var/adm/cleanup.log.

### Cleanup program completed at 11/22/33  15:13:22

PHCO_34974 is a cumulative SAM patch and PHCO_31590 is a libpam_hpsec patch.

Is it safe for me to issue out cleanup -c 2 command..?

Thank you,

Molly Williams.

[Dennis Handly]

>Is it safe for me to issue cleanup -c 2 command?

It is safe to use -c 1. When was the last time you removed a patch and how long have the existing patches been there?

[mollywilliams]

> When was the last time you removed a patch and how long have the existing patches been there?

I have never removed patches and the patches were there since 4 Aug 2009. There are 3 patched dated 10 Oct 2009.

Thank you

Molly Williams.

[Bill Hassell]

The / (root) filesystem should always be essentially static in size, about 300-500 MB in size. /var is a constantly varying filesystem and is always recommended to be separate. The root filesystem cannot be expanded in place without severe risk. Note also that you cannot remove any files from /var/adm/sw without using cleanup as this would corrupt the installed software/patch database.

The recommended way to fix this is to use your Ignite backup tool to restore vg00 and using the layout features that are part if the restore menu to give /var a separate lvol. I assume you are taking regular Ignite backups in addition to full backups.

/var can change rapidly in size and needs regular maintenance such as trimming logs, removing duplicate print jobs, trimming email, and application housekeeping. If it gets full, many programs and applications will fail, but when it is a separate lvol, it can be expanded.