/var & /var/adm/sw filesystems

[John Jayaseelan]

Hi,

The /var & /var/adm/sw file systems are used by system for maintaining the SW installation and deinstallation.

Please tell how this directories are used and on which sequence during SW installation and deinstallation.

Is it possible to just deinstall one particular deinstallation of patch from a bundle of patch installation?

The /var file systems is full, is there anyway some space can be created by purging some files.

Thanks

[Robert-Jan Goossens · Accepted solution]

John,

The easiest way is to use the cleanup command.

# cleanup -p -c2
-p preview
-c Commit patches superseded at least times.

Regards,
Robert-Jan

[Marco Santerre]

/var/adm/sw more particularly is used to store anything related to what has been installed on your system using the swagent.

If you want to clean some space, you may want to use the cleanup command which will commit patches that have been on your system and erase them from your /var/adm/sw/save directory.

[Kevin Daines]

To the best of my limited knowledge! you can uninstall certain patches and SW individually so long as they are listed individually in the swlist.

[Helen French]

Yes, normally the patches goes to this file system (/var) and the log files for the applications. There is no safest solution to uninstall patches from /var other than 'cleanup' command:

# cleanup -c 1
# man cleanup

In case /var is full, check for large log files and trim it (wtmp, utmp, syslog.log, mail.log etc). Check /var/adm/crash for big crash files and clean it up. Also, run cleanup command to remove very old patches from system which were superceded.

[John Jayaseelan]

Hi,

The cleanup seems to clearing from /var/adm/sw but not from /var.

Thanks

[Marco Santerre]

Chances are that measn you have two separate file systems, right? one is /var/ the other one is /var/adm/sw.

One of the things I would do is check for old core file : find /var -name core, and if you find any delete them.

[Helen French]

You need to check if those are two different file systems:

# bdf
# cat /etc/fstab

If they are one single file system (/var), then either increase your LV size (lvextend) or trim your log files. You can check for big files in a directory with:

# find /var -xdev -depth -size +10000 -exec ll {} \; > /tmp/big_files

[John Jayaseelan]

Hi,

/var & /var/adm/sw are seperate filesystems.


What goes onto /var directory during the SW installation, Need to create some space on /var.

Thanks

[John Jayaseelan]

Hi,

find /var -xdev -depth -size +10000 -exec ll {} \; returned following, which files can be removed without any functional impact on the system.

-rw-r--r-- 1 root root 16598676 Jun 10 2002 /var/adm/crash/crash.
2/vmunix
-rw-r--r-- 1 root root 67092480 Jun 10 2002 /var/adm/crash/crash.
2/image.1.1
-rw-r--r-- 1 root root 67100672 Jun 10 2002 /var/adm/crash/crash.
2/image.1.2
-rw-r--r-- 1 root root 67100672 Jun 10 2002 /var/adm/crash/crash.
2/image.1.3
-rw-r--r-- 1 root root 67080192 Jun 10 2002 /var/adm/crash/crash.
2/image.1.4
-rw-r--r-- 1 root root 67084288 Jun 10 2002 /var/adm/crash/crash.
2/image.1.5
-rw-r--r-- 1 root root 67100672 Jun 10 2002 /var/adm/crash/crash.
2/image.1.6
-rw-r--r-- 1 root root 67080192 Jun 10 2002 /var/adm/crash/crash.
2/image.1.7
-rw-r--r-- 1 root root 28770304 Jun 10 2002 /var/adm/crash/crash.
2/image.1.8
-rw-r--r-- 1 root root 7327330 Oct 10 2002 /var/adm/crash/crash.3
/vmunix.gz
-rw-r--r-- 1 root root 7321917 Oct 10 2002 /var/adm/crash/crash.3
/image.1.1.gz
-rw-r--r-- 1 root root 10233930 Oct 10 2002 /var/adm/crash/crash.
3/image.1.2.gz
-rw-r--r-- 1 root root 13869686 Oct 10 2002 /var/adm/crash/crash.
3/image.1.3.gz
-rw-r--r-- 1 root root 13608440 Oct 10 2002 /var/adm/crash/crash.
3/image.1.4.gz
-rw-r--r-- 1 root root 19993129 Oct 10 2002 /var/adm/crash/crash.
3/image.1.5.gz
-rw-r--r-- 1 root root 13738429 Oct 10 2002 /var/adm/crash/crash.
3/image.1.6.gz
-rw-r--r-- 1 root root 14556868 Oct 10 2002 /var/adm/crash/crash.
3/image.1.7.gz
-rw-r--r-- 1 root root 7327330 Nov 7 2002 /var/adm/crash/crash.4
/vmunix.gz
-rw-r--r-- 1 root root 7856711 Nov 7 2002 /var/adm/crash/crash.4
/image.1.1.gz
-rw-r--r-- 1 root root 10074798 Nov 7 2002 /var/adm/crash/crash.
4/image.1.2.gz
-rw-r--r-- 1 root root 13984989 Nov 7 2002 /var/adm/crash/crash.
4/image.1.3.gz
-rw-r--r-- 1 root root 35224228 Nov 7 2002 /var/adm/crash/crash.
4/image.1.4.gz
-rw-r--r-- 1 root root 15362798 Nov 7 2002 /var/adm/crash/crash.
4/image.1.5.gz
-rw-r--r-- 1 root root 14605827 Nov 7 2002 /var/adm/crash/crash.
4/image.1.6.gz
-rw-r--r-- 1 root root 15213991 Nov 7 2002 /var/adm/crash/crash.
4/image.1.7.gz
-rw-r--r-- 1 root sys 15526862 Jun 24 2002 /var/opt/ignite/logs/
makrec.log2
-rw-rw-rw- 1 root sys 15784439 Jun 24 2002 /var/opt/ignite/recov
ery/arch.include
-rw-r--r-- 1 root root 7636528 Dec 9 15:40 /var/opt/perf/datafile
s/logglob
-rw-r--r-- 1 root root 9247304 Dec 9 15:40 /var/opt/perf/datafile
s/logappl
-rw-r--r-- 1 root root 17749456 Dec 9 15:40 /var/opt/perf/datafil
es/logproc
-rw-r--r-- 1 root root 8022280 Dec 9 15:40 /var/opt/perf/datafile
s/logdev
-rw-rw-rw- 1 root sys 13297811 Oct 31 14:18 /var/opt/perf/datafil
es/mwalogs.tar.gz
-rw-rw-rw- 1 root sys 15510823 Jun 24 2002 /var/tmp/arch.include
.1

Thanks