How to determine temporal LIF volume space requirements a priori?

[Ralph Grothe]

Hello,

I'm failing to write an Ignite tape because of alleged missing file space in the default temporal LIF volume storage stage under /var/tmp.

# tail -12 /var/opt/ignite/recovery/latest/recovery.log
* Creating The Tape Archive
* Checking configuration file for Syntax
lifcp: Cannot create SYSCMDS ; no space on the LIF volume
make_medialif: error - lifcp SYSCMDS failed, probable insufficient size for /var/tmp/uxinstlf.recovery

ERROR: System Error, /opt/ignite/bin/make_medialif failed creating boot LIF
file.
ERROR: Failed to generate LIF on tape .



======= 06/12/05 13:46:03 METDST make_tape_recovery completed unsuccessfully


According to make_tape_recovery's manpage only some 32 MB should suffice while make_medialif's claims from 100 KB with some variation.

Because of lack of OnlineJFS on this box I even had to bring it down to maintenance mode to extend the /var FS.

I thought the new size should be more than sufficient:

# bdf /var/tmp
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol7 1048576 754033 276580 73% /var

I know from the manpage that I could point to another staging area for the LIF volume through the -B switch.
But I would like to keep it all in the usual default place, and thus reuire to know how much further I will have to extend the /var FS.

I haven't found a dryrun switch for make_medialif to have an a priori estamate of space consumption.
Would it be possible to have it written to stdout so that I could pipe it to wc to count the bytes?

Regards
Ralph

[Robert-Jan Goossens]

Hi Ralph,

Check this doc.

make_medialif script error - lifinit -v72000000 too small a value
Document id: 8606267269

http://www5.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000073734689

Regards,
Robert-Jan

[Thayanidhi · Accepted solution]

If I am correct it's not a actual space problem. You need one the below patch depends on the hp-ux version.

11.00: PHSS_27407
11.11: PHSS_27406

Regds
TT

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=437608

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=178002

http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000073838490

[Eknath]

Hi Ralph,

check /opt/ignite/bin/make_medialif for -v value. Increase this value to 95000000.
Increase it again if you get same error message...

Cheers!!!
eknath

[Ralph Grothe]

Thayanidhi,

it was exactly the patch you mentioned that fixed this bug.

Robert-Jan & Eknath,

your suggestions probably boiled down to
manually hacking what the above patch incorporated.

I could only see that the -v value given to lifinit now is bigger than your suggested increase.


# swlist -l fileset -a title -a install_date -a state PHSS_27407|grep -v ^#

PHSS_27407.MGMT-TOOLS Ignite-UX.MGMT-TOOLS 200506141357.25 configured

# tail -3 /var/opt/ignite/recovery/latest/recovery.log

======= 06/14/05 16:18:51 METDST make_tape_recovery completed successfully!


# grep -n ^lifinit /opt/ignite/bin/make_medialif
507:lifinit $ipl_options -v102000000 -d24 -nISL10 -K2 -s4096 $lif_file ||