make_tape_recovery problems

[zhi wang_1]

I am trying to run a make_tape_recovery on a HP9000/B2000 workstation with O/S 10.20. However, within a couple of minutes the /var file system will be filled up to 100% full although there is over 120MB diskspace available before I kicked off the job. And HP recommends that the minimum free disk space under /var should be around 40MB. FYI: Last year I ran the same job twice on this box and had no problem at all.

My understanding is that the make_tape_recovery will create a list of all the filenames under /var/opt/ignite/recovery called flist. Once the flist is complete, it will "tar" those files and write to tape. What puzzles me is that we have another HP9000/B2000 workstation with the exact configuration and system resource. I ran make_tape_recovery only last week. The flist file only used about 5MB. We had about 140MB available under /var before the job kicked off. The job ran to its completion without any problem.

At first HP suggested that I upgrade to a newer version of Ignite-UX, which I did. But the problem continues.

Has anybody experienced similar problems? Your help will be greatly appreciated.

[Ravi_8]

Hi,

which version of ignite are you using?

recent ignite release should solve this problem

[Victor BERRIDGE]

Hi,
What options are you using?

Regards
Victor

[James R. Ferguson]

Hi:

Your '/var' free space is pitifully low. If you can't expand it, try regaining space by trimming log files like 'var/adm/wtmp' and '/var/adm/btmp', and running 'cleanup' this may gain you the space you need.

Since this is 10.20, run 'cleanup' without any arguments.

Regarde!

...JRF...

[zhi wang_1]

I am using
Ignite-UX A.3.7.95 HP-UX System Installation Services
InstantIgnite B.10.20 Instant Ignition

And here is the command I used: #make_tape_recovery -a /dev/rmt/0mn -x inc_entire=vg00

[zhi wang_1]

The /var may be low on diskspace. But increasing diskspace does not seem to be a "convincing" solution. The reason: we have an identical box with identical resource/configuration (see my original message.

[Steven E. Protter]

You can clear disk space in /var by trimming log files and such.

Many machine operations will FAIL without adequate space on /var It stands for variable files, some of which can get quite large.

A quick way to clear space is.

sam
routine tasks
System Log Files

It can trim those logs and clear space.

Current Ignite for 11.11 is 4.1.62

Make sure you don't hae the latest pax patch in, or you won't be able to use the tapes.
PHCO_26422 Is a big no no here.


SEP

[Victor BERRIDGE]

Have you tried a silly
make_tape_recovery -Av
There you should see whats going on, no?

All the best
Victor

[Helen French]

Couple of things to try:
1) Before you install the ignite software, apply the latest patches to the system including pax(1) patch.
2) Run make_tape_recovery with -v (verbose) and see what actually happens during the process.
3) What's the total /var space? if it's very high and if the free space is very small compared to the total space, then 'bdf' will report the file system as 100%.
4) Check the file system space with du command before and after the command execution. See which directory is getting full.
5) You might need to think about increasing space on /var.

[Bernhard Mueller]

Hi,

to me it looks like you have a problem with the "Boot Destination File". By default this is /var/tmp/uxinstlf.recovery.

Try the -B option to point this to a different file system where you have more space (you only need it temporarily, that's why it should go into /var/tmp actually).

After you start make_tape_recovery watch this file which you specified with -B.

Regards,
Bernhard