Ignite tape creation

[Indira Aramandla]

Hi,

I am trying to create an ignite tape using make_recovery -A -v -C -d $TAPE_DEVICE. And in this process while creating the configuration file, it fails saying ".make_recovery(390): Call to /opt/ignite/bin/save_config failed". I have checked the logs and found that mkfs while creating the file system did not determine the proper size (either SHORT or LONG) and fails as a result with the following error message fatal "unable to determine file system length"

Can any one provide info regarding and what has to be done. We create the ignite tape once every week on the PROD server HP 9000 K360 class

When tried to do the same on the DR server which is another similar server HP 9000 K360 class.

[Michael Steele_2]

The 390 message indicates a problem with the volume group. Use vgdisplay to check that the Curr and Open LV's equal.
#vgdisplay /dev/vg##
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 8 <---
Open LV 8 <---

Also,
...strings /etc/lvmtab.

Cross reference the disks seen in each vg with the disks listed via vgdisplay. lvmtab may be corrupt. If so, mv /etc/lvmtab /etc/lvmtab.old

vgscan -p -a -v (* preview *)
verify output

Then, when sure:

vgscan -a -v (* generates a new lvmtab when no -p *)

[Sridhar Bhaskarla]

Hi,

First thing I would suggest is to install new version of ignite. It comes with make_tape_recovery that is much more efficient than make_recovery. You can get it from the following site..

http://www.software.hp.com/products/IUX/faq.html

This error is resulting from save_config command. This is a shell script and run it with -x option to see where it is failing.

cd /opt/ignite/bin
sh -x save_config

See if you have any unmounted filesystems in vg00. If you have and if you are not going to use them, delete them. Else mount them on some temporary mount points.

-Sri

[Indira Aramandla]

Yes I ahve seen the logs and found that it was failing when Creating the configuration file. i.e save_config. That is what I said in the question. And the point it is failing is when it does the mkfs to determine the file system legth, it checks if the size is SHORT or LONG and it comes to the else condition and says "fatal "unable to determine file system length".

[Steven E. Protter]

On 11.11 systems save_config can fail due to a conflict with VXFM volume manager.

IF you aren't using it, you can safely remove that software, reboot your box and the Ignite tape will work.

I had the same problem and that is how we solved it. (Rabbit alert!)

SEP

[Michael Duthie]

Indira,

Perform a "mkfs -F hfs -m /dev/vg00/rlvolX" on every hfs filesystem.

One of them does not report a -S or -L, it need to be fixed. Then your make_recovery should work.

[Indira Aramandla]

Hi Mike,

Yes I think one of them does not report a -S or -L. So how do I fix it. Please provide some steps.

[Michael Duthie]

Have you found the offending lvol ? if so what is the mksf output, a tunefs -v would be usefull too.

[Indira Aramandla]

Mike,

I performed a "mkfs -F hfs -m /dev/vg00/rlvolX" on every hfs filesystem and did not get any output. Where does it output the filesystem lengh. Is there a log or does it output to the screen

[Michael Duthie]

The output goes to the screen, no output from mkfs indicates a problem. My output looks as follows -

root@hpmanf33:/ # tunefs -v /dev/vg00/rlvol1
super block last mounted on: /stand
magic 95014 clean FS_OK time Fri Nov 15 13:57:29 2002
sblkno 16 cblkno 24 iblkno 32 dblkno 136
sbsize 2048 cgsize 2048 cgoffset 32 cgmask 0xfffffff0
ncg 115 size 614400 blocks 600571
bsize 8192 bshift 13 bmask 0xffffe000
fsize 1024 fshift 10 fmask 0xfffffc00
frag 8 fragshift 3 fsbtodb 0
minfree 10% maxbpg 168
maxcontig 1 rotdelay 0ms rps 60
csaddr 136 cssize 13312 csshift 9 csmask 0xfffffe00
ntrak 12 nsect 28 spc 336 ncyl 1829
cpg 16 bpg 672 fpg 5376 ipg 832
nindir 2048 inopb 64 nspf 1
nbfree 12565 ndir 48 nifree 95217 nffree 242
cgrotor 4 fmod 0 ronly 0
fname fpack
featurebits 0x1 id 0x0,0x0
optimize FS_OPTTIME

cylinders in last group 5
blocks in last group 210

root@hpmanf33:/ # mkfs -F hfs -m /dev/vg00/rlvol1
mkfs -F hfs -L /dev/vg00/rlvol1 614400 28 12 8192 1024 16 10 60 6427
root@hpmanf33:/ #


Does tunfs -v work ?


Mike

[Indira Aramandla]

Hi Mike,

I am sorry for the delayed reply. tunfs -v does not work either.

[Michael Duthie]

whoops ... tunefs -v

[Indira Aramandla]

Yes it does work.

It displays the following. I did for one volume group.
super block last mounted on: /usr
magic 95014 clean FS_OK time Wed Mar 19 16:45:34 2003
sblkno 16 cblkno 24 iblkno 32 dblkno 80
sbsize 2048 cgsize 2048 cgoffset 24 cgmask 0xfffffff8
ncg 260 size 638976 blocks 622293
bsize 8192 bshift 13 bmask 0xffffe000
fsize 1024 fshift 10 fmask 0xfffffc00
frag 8 fragshift 3 fsbtodb 0
minfree 10% maxbpg 77
maxcontig 1 rotdelay 0ms rps 60
csaddr 80 cssize 27648 csshift 9 csmask 0xfffffe00
ntrak 7 nsect 22 spc 154 ncyl 4150
cpg 16 bpg 308 fpg 2464 ipg 384
nindir 2048 inopb 64 nspf 1
nbfree 11581 ndir 1140 nifree 76296 nffree 3996
cgrotor 21 fmod 0 ronly 0
fname fpack

cylinders in last group 6
blocks in last group 115

Now what should I look for. Does any of the above information provide the file system length.

[Michael Duthie]

could be /sbin/fs_wrapper corrupt.

what does ll /sbin/fs_wrapper look like.

I have a size of 192512

[Indira Aramandla]

Yes Mike, it looks like it. /sbin/fs_wrapper is 0 bytes.

On the server where I can successfully create the ignite tape the fs_wrapper is 159744 bytes and on the server where I have problem with ignite tape creation it is 0 bytes.

[Michael Duthie]

If both systems are the same version of HPUX then just copy it across.

[Indira Aramandla]

Thanks for all your replies. Problme solved. Closing the thread.

Indira A