make_recovery problems

[Cliff Peters]

Hi all,

I have a number of problems stemming from needing to increase /stand prior to applying the Dec2002 bundle to a K580.
I have increased /var and /usr ok.
I have read all the forums on /stand and want to create a make_recovery tape (DLT7000) to boot from , then use Ignite to extend /stand.
I also have the latest Ignite.

The logs generated by make_recovery contained no errors.
However I was running make_recovery without the no-rewind device then when booting from the tape non-interactively I received the error messages:
/i2 short by 3004MB (this is an application fs)
/home short by 164MB
contiguous allocation required for dump lv
free space in /var < 25% of memory

Realising the tape should use a no-rewind device I created another tape.

Then using mt to compare the tapes , they were identical!

So , my questions are:-
are the tapes identical?
did I overwrite the lif by not using no-rewind?
how can I tell what is on the tapes?
looking at the bdf , why did the first two errors appear?
as this is a test machine , I assume the last two errors are less urgent?

The bdf is as follows:

Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 83733 41418 33941 55% /
/dev/vg00/lvol1 47829 31764 16065 66% /stand
/dev/vg00/lvol8 1152909 471609 566009 45% /var
/dev/vg00/lvol7 1049173 518016 426239 55% /usr
/dev/vg00/lvol6 122821 71156 39382 64% /tmp
/dev/vg00/lvol5 4085269 433266 3243476 12% /opt
/dev/vg00/lvol9 7185124 3895058 2571553 60% /i2
/dev/vg00/lvol4 8211018 3441786 3948130 47% /home


Any help would be appreciated.

Thanks
Cliff

[Pete Randall]

Cliff,

My assumption would have to be that this all stems from not using the no-rewind device. My first step would be to try recovering from the second (correct) tape and see what that one says. It's going to be very hard to diagnose otherwise.


Pete

[Cheryl Griffin]

The messages "/home short by" are an indication that when restoring from the tape, you need to go into interactive mode, advanced filesystem tab and resize/verify the size definitions for these logical volumes.

When not using a no-rewind device, Ignite should have errored and not created the tape to begin with. So this sounds very strange. Maybe you did use the correct device?
Maybe the device is really a no=rewind which would be possible if it had been made with mknod vs. insf? # lssf /dev/rmt/0m
The normal error is:
make_recovery(284): Invalid -d /dev/rmt/0m

If a tape had been created with the wrong device anyway, the archives between tapes would look the same but the LIF may not. To view the contents of the tape including the LIF:
# dd if=/dev/rmt/0mn of=bootimage bs=2k
# lifls -l bootimage
# mt -f /dev/rmt/0mn rew
# mt -f /dev/rmt/0mn fsf 1
# tar tvf /dev/rmt/0mn

[Cheryl Griffin]

And always use the most current version of Ignite http://www.software.hp.com/products/IUX/download.html which currently is B.4.1

[Tim Sanko]

Ok if you specified the tape, then you may have a problem, if you used the command
"make_recovery -Av" you have no problem. if you specified the device and you didn't use a no rewind device, try booting from the second tape. Conversely, you could rerun Ignite, and check to see if it writes the LIF and then if it writes the filesystem. watch to see if after it writes the LIF the tape rewinds. Check also if all your filesystems were dumped.

If you really need to know if the tapes are identical, use dd to recover to a large filesystem (24 GB is enough for a large Ignite tape). dump both images and check sizes. dd should dump all the data to the EOM mark on the tape...


Tim

[Cliff Peters]

Cheryl,

I have re-run make_recovery and viewed the contents of the tape as you advised and all looks ok.
I then tried booting from the tape and received the same errors.
So , before I extend the file systems , why should I need to , when /i2 is 60% used and /home is 47% used??

Thanks
Cliff