topic Re: VX patch install using too much space in / in Operating System - HP-UX

VX patch install using too much space in /

Michelle Barton — Fri, 05 May 2006 10:16:11 GMT

We accidentally installed some vx patches, PHCO_30850, PHCO_31203 and PHKL_30756 which caused the /etc/vx directory to use 60mb. Our production systems only have a 200mb / , so we are struggling with space. Short of unininstalling thes patches, anyone have ideas on what I could do to free up the space? We tried removing it, but apparently onlineJFS and bootup uses some pieces in here. We are not using VX as our filesystem manager, we use LVM. Thanks...Michelle

Re: VX patch install using too much space in /

Simon Hargrave — Fri, 05 May 2006 10:23:21 GMT

200Mb should be sufficient. I'd be tempted to check for other things in / taking up space.

Check for core files: -

find / -name *core* -xdev

Check for large files example is > 10Mb): -

find / -size +10000000 -xdev

It's not uncommon for misplaces files to fill up /.

Re: VX patch install using too much space in /

melvyn burnard — Fri, 05 May 2006 15:30:40 GMT

Take a look in /dev/to make sure there are no normal files in there. A common error is for someone to do a tar backup, and specify an incorrect target file, which ends up being a large normal file in /dev, e.g.:
cd /home/mydir
tar cvf /dev/rmt/om *

This means that you get a normal file om in /dev/rmt instead of it going to teh tape at /dev/rmt/0m

Re: VX patch install using too much space in /

Michelle Barton — Fri, 05 May 2006 15:35:07 GMT

I decided to gzip some of the files under /etc/vx after testing. This reduced the dir from 60mb to 20mb. When you're talking only 200mb filesystem, that's pretty good.

Thanks!

Re: VX patch install using too much space in /

Geoff Wild — Fri, 05 May 2006 16:25:32 GMT

From a call I placed last year:

there is a S.R. on that -- you can't remove it
VERITAS have recently released a 11.11 VxVM 3.5 patch
[PHCO_30850/PACHRDME/English] which installs a 29MB file at
"/etc/vx/static.d/build/vold.o". The huge vold.o is due to the inclusion
of debug symbols as a result of JAGaf37554. This object file is
necessary for recompiling a static vxconfigd binary (under
/etc/vx/type/static/vxconfigd) in case some VERITAS ASL (array support
library) is installed. The huge vold.o is due to the inclusion of debug
symbols as a result of JAGaf37554. The static vxconfigd recompiled using
this vold.o is also 29MB in size. That means the installation of
[PHCO_30850/PACHRDME/English] will request 29*2MB in the root
filesystem for customers having an ASL installed. That creates a lot of
burden on the root filesystem which is currently defaulted at <300MB.

It is known that pxdb can optimize the debug information in the
recompiled static vxconfigd to reduce its size to 5MB. For systems
having the compiler bundle installed, ld will find pxdb under the
default path /opt/langtools/bin/pxdb and will run pxdb automatically on
the executable. But the intermediate program would still be 29Mb before
it was pxdbed.
Although [PHCO_30850/PACHRDME/English] is a 11.11 patch, VERITAS will
be including the debug symbols in vold.o for VxVM patches on 11.23 and
later VxVM releases, thus this request to increase the default root
filesystem size on 11.23 and onwards. VERITAS also wants to increase the
default size of the stand filesystem at the same time as both root and
stand filesystems cannot be easily extended.
CR# JAGaf51230 problem This enhancement request is asking for the
default sizes for the root filesystem and /stand to be changed and also
(optionally) to allow /etc/vx/static.d/build to be a mounted filesystem.

Rgds...Geoff