Operating System - HP-UX
1830623 Members
2373 Online
110015 Solutions
New Discussion

Ignite file system size problem

 
Mark Fisher_4
Frequent Advisor

Ignite file system size problem

I'm having a problem using the ignite interface to change the size of filesystem. I used the procedures here in ITRC to make_sys_image of one server and am attempting to ignite a second server with this image. I used the technique to create a "golden image" along with it's config file. I ran archive_impact to determine the impacts in the config file. The impacts of the config file look like this:

impacts = "/" 649Kb
impacts = "/.ssh" 1Kb
impacts = "/.sw" 39Kb
impacts = "/dev" 20Kb
impacts = "/etc" 95711Kb
impacts = "/home" 46521Kb
impacts = "/omzsv2" 3Kb
impacts = "/omzsv3" 12482Kb
impacts = "/opt" 2954850Kb
impacts = "/sbin" 121906Kb
impacts = "/stand" 106246Kb
impacts = "/tmp" 153047Kb
impacts = "/usr" 2764347Kb
impacts = "/var" 1249577Kb


When I attempt to ignite the new server, the file system sizes do not match this. The worst problem is the / (root) filesystem is 16668MB large and ignite will not let me change the size.

Then I look in the clients directory under /var/opt/ignite/clients and the config file that was created for this newly created client has the root file system at 16668MB.

I have no idea why it does this. I tried completely removing the cleint from ignite and verify it's client dir is deleted. For some reason it always seems to create these config files for the client with HUGE filesystem sizes. I ran into this last week when setting up two other servers.

Any help would be greatly appreciated...
5 REPLIES 5
Sameer_Nirmal
Honored Contributor

Re: Ignite file system size problem

There is default disk and filesystem layout defined in
/opt/ignite/data/Rel_B.11.11/config
Defaults to all clients are defined in
/var/opt/ignite/config.local

Check these two files. I am sure somewhere the root filesystem size 16668MB is defined.

Fabio Ettore
Honored Contributor

Re: Ignite file system size problem

Hi,

if your goal is extend the root filesystem then I suggested you the procedure from another ITRC doc:

VIKBRC00010528 - Sys Adm: Using Ignite-UX to extend /stand or / filesystem?

You should backup your system by make_tape_recovery and then change parameters (the size of the root filesystem) like the doc.
I know that procedure works fine.

Hope this helps you.

Best regards,
Fabio
WISH? IMPROVEMENT!
Mark Fisher_4
Frequent Advisor

Re: Ignite file system size problem

I was able to edit the /var/opt/ignite/config.local and add the sizes for all the lvols/filesystems. I know ignite read the file because the first time it complained about syntax issues. After that was fixed it still did not use these parameters. The config files /opt/ignite/data/Rel_B.xx.xx are very complicated scripts and I did not touch them.

The problem is I start with a brand new client in ignite with nothing in it's directory. After lanbooting the client from the ignite server and getting the advanced configuration GUI to display, a config file gets created forthe clitnt with with extrememly large file system sizes; especially root. Any attempts to change the size to a smaller value fail as ignite complains. I think it's kind of crazy to have a 16GB root file system.

The ignite server is C.6.1.44...

any other ideas?
Sameer_Nirmal
Honored Contributor

Re: Ignite file system size problem

It seems that the variable assignment of root disk is set to default which doesn't allow you to change the layout of root disk.

Check for the variable _hp_root_disk in the /var/opt/ignite/clients//config and config.local file . It should have init before it . i.e.
init _hp_root_disk=""

This would allow to change the layout of root disk in the GUI.

The weired size 16668MB is being calculted wrongly by Ignite-UX .Is your system patched to the recomended patch level ?


Mark Fisher_4
Frequent Advisor

Re: Ignite file system size problem

we (HP Support) found a workaround that you can place in the configs:

_hp_ignore_sw_impact=1

I'll be upgrading soon to C.6.2.241 and well see if this was a bug in C.6.1.44