disk space /var dir almost full : arch.include.1 ?

[Franky Leeuwerck]

Hello everyone,

We are running out of diskspace on the /var volume which contains a big file arch.include.1

Can we delete it ? I don't know what its purpose is.

Thanks in advance.
Franky Leeuwerck

[Tom Geudens · Accepted solution]

Hi Franky,
/var/tmp/arch.include.1 is something used by make_net_recovery. It shouldn't be enormous though. Deleting it is probably not going to solve your problem (as it will probably reappear).
Did you search for "core" files underneath /var ?
You might also have some softwares underneath /var that can be "moved" to their own filesystems. We did this (for example) with /var/opt/perf.

Regards,
Tom

[Franky Leeuwerck]

Thanks for the feedback Tom.


Franky

[Rainer von Bongartz]

arch.include.1 comes from your last make_recovery run and is the archive of all files used by the make_recovery process.

you can remove it without any problems

Regards
rainer

[T G Manikandan]

You can do a

#du -k /var|sort -nr >/tmp/var.du

find the files that are really big and remove them.

Just check your /var/adm/crash directory.

The files regarding the system crash are stored here .
Empty this directory.

ALso remove the unwanted files from /var/tmp and /var/preserve directories.


Also do a cleanup of your old patches.

check for man pages of cleanup.

ALso commit all the patches using
#swmodify -x patch_commit=true \*

Also check your /var/opt/OV directories.
If they are using huge size you can mount them as a seperate file system.
/var/opt/OV are the openview directories.

Also check your
/var/mail /var/adm/syslog/
directories for large files.

Also check your
/var/adm/wtmp file size.

ALso check for core files in the file system and remove it.

Thanks

[T G Manikandan]

You can remove the /var/tmp files
using

files which are not accesed let's say in 7 days.
# find /var/tmp -atime +7 -exec rm {} \;


Thanks

[Bill Thorsteinson]

Check /var/adm and its subdirs for large files.
Compress or delete old files.
Rename current.log files
and sent the syslog daemon a
HUP signal.

Get logrotate from the porting center to keep your log files
trimmed to a reasonable size.

Get logcheck to scan the log files and notify you if there
is anything interesting.

[Marc Litaudon]

Hello Franky,

1. You may use a different "temporary directory" as default "/var/tmp", e.g.

/opt/ignite/bin/make_tape_recovery -B /var/adm/crash/uxinstlf.recovery

2. The "quick & dirty" : this default value can be changed in script "/opt/ignite/bin/make_medialif", e.g. "TMP_DIR=/var/adm/crash"

3. In your "little cleanup" steps, think of
"/var/preserve", wich may contain old temporary files, used by "vi" editor, in "recover" mode.