root file system and /etc.lvmconf file

[John Jimenez]

As I increase the sizes of my volume groups the root directory seems to be filling up. It is at 91% now. In the following thread

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1369373

it is mentioned that The two largest directories are /sbin and /etc. here is cut and paste of the top output. as volue systems get larger and larger conf and conf.old files in /etc/lvmconf is the one growing. I do not think I have any choice do get larger disks and make recover with and ignite tape. But if anyone has another idea please advise. thanks.

=> #du -kx | sort -rn | head -20
241320 .
188000 ./etc
67744 ./etc/lvmconf
63624 ./etc/vx
49168 ./sbin
36568 ./etc/opt
33112 ./etc/vx/type
29544 ./etc/opt/resmon
29480 ./etc/vx/static.d
28768 ./etc/vx/static.d/build
17840 ./etc/opt/resmon/lib
14984 ./etc/vx/type/static
10416 ./etc/lp

[Steven E. Protter]

Shalom,

I'd look at /etc/ specifically lvmconf and vx and see whats there. It seems possible that there is a large file sitting there that probably does not belong.

uname -r
uname -a

bdf /

Please post the abovbe so we can get a perspective and help you.

SEP

[James R. Ferguson · Accepted solution]

Hi John:

> conf.old files in /etc/lvmconf is the one growing.

You could discard the "*.old" files in this directory. The default action of the LVM commands is to run 'vgcfgbackup' every time. Thus, the current LVM configuration and the previous one are saved in this directory.

Regards!

...JRF...

[John Jimenez]

Hi SEP Thanks for the input. I do not see anything added in /etc/vx but /etc/lvmconf has *conf and *conf.old. also mapfile, but mapfiles are not very big.

=> #uname -r
B.11.11
root@diamond.iehp.org:/etc/vx>
=> #uname -a
HP-UX diamond B.11.11 U 9000/800 340828412 unlimited-user license
root@diamond.iehp.org:/etc/vx>
=> #bdf /
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 270336 246128 24064 91% /

[John Jimenez]

Hi JRF. I was hoping I could get rid of the conf.old. But the dates on these file are recent, so I have a feeling that they will some how regenerate again in the future.

[James R. Ferguson]

Hi (again) John:

I was hoping I could get rid of the conf.old. But the dates on these file are recent, so I have a feeling that they will some how regenerate again in the future.

Re-read what I first wrote: the default action for any LVM command is to create a new backup of the volume group's configuration. Hence adding two logical volumes to a volume group would result in two '/etc/lvmconf' files for that volume group. See any of the LVM manpages.

Regards!

...JRF...

[John Jimenez]

Cool. I will check them out. thanks again.

[Bill Hassell]

This is a feature of LVM and a lot of LUNs (disks) and volume groups. The root filesystem is usually large enough for a few dozen disks and 5 or 6 VGs. But as your system grows with more disks and VGs, lvmconf will grow -- a lot. a 300 MB / directory is too small for 20 VGs and 500 disks. This is also true for LUNs with alternate links where the links must be present in the VG. New path managers pick a single CTD for each LUN and the rest of the alternate paths are handled behind the scenes.

The /etc/ directories look normal but at some time in the future, you'll probably need to use Ignite to expand the / directory. I would double the current size.

[sujit kumar singh]

Hi


This sort of issues as well as others require the root fileystem to be larger thats why this time when you are igniting the systen for a larger / , make sure that that is comfortably larger that you do not have to face such issues again in future.

can you also give bdf as well as vgdisplay -v vg00
regards
sujit