IGNITE-UX backup

[HPquestion]

We have Integrity Rx4640 , HP-UX ricr3itg B.11.23 U ia64.

In the old Ignite version (B5725AA C.6.9.141 HP-UX Installation Utilities (Ignite-UX)
while doing make_tape_recovery -Av we were getting the below error.

/opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2008-05-01,13:56/system_cfg vg00
/opt/ignite/bin/save_config[217]: 19340 Floating exception(coredump)
save_config: Error - cannot determine lv "/dev/vg00/lvol9" usage via fstyp
ERROR: /opt/ignite/bin/save_config failed


Then we have upgraded the Ignite version to C.7.5.142 .While doing the backup in this version by

make_tape_recovery -x inc_entire=vg00

we are getting the below error
/var/opt/ignite/recovery/2008-05-08,10:01/system_cfg vg00
/opt/ignite/bin/save_config[146]: 12449 Floating exception(coredump)

Then we did fstyp on the following logical volumes.Found all retured vxfs except lvol2 and lvol9.

/dev/vg00>ls
group lvol1 lvol6 lvoracle lvsapmnt rlvmirrlogC rlvol4 rlvol9 rlvoriglogC
lvmirrlogA lvol2 lvol7 lvoriglogA lvstage rlvmirrlogD rlvol5 rlvoraITG rlvoriglogD
lvmirrlogB lvol3 lvol8 lvoriglogB lvusrsap rlvol1 rlvol6 rlvoracle rlvsapmnt
lvmirrlogC lvol4 lvol9 lvoriglogC rlvmirrlogA rlvol2 rlvol7 rlvoriglogA rlvstage
lvmirrlogD lvol5 lvoraITG lvoriglogD rlvmirrlogB rlvol3 rlvol8 rlvoriglogB rlvusrsap


@/sapbasis/uxcmds>fstyp /dev/vg00/lvol9
Floating exception(coredump)

@/sapbasis/uxcmds>fstyp /dev/vg00/lvol2
UX:vxfs fstyp: ERROR: V-3-20012: not a valid vxfs file system
unknown_fstyp (no matches)

What we should do? Any help will be greaty appreciated. Thanks!

[Patrick Wallek · Accepted solution]

The error for lvol2 doesn't surprise me since that is your primary swap space. That will not have a file system on it, so don't worry about it.

lvol9 is interesting. Is that LV mounted? What does the line in /etc/fstab look like? What does the following command return?

# mkfs -m /dev/vg00/lvol9

That command will tell you exactly how the filesystem was created on that LV.

[Steven E. Protter]

Shalom,

I'd say the filesystem is either not mounted or corrupted.

If it is mounted, umount it and maybe run fsck.

If its not mounted but in fstab, mount it.

SEP

[HPquestion]

Actually lvo12 and 19 are part of SWAP.

swapinfo -tam
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 4096 0 4096 0% 0 - 1 /dev/vg00/lvol2
dev 16000 0 16000 0% 0 - 0 /dev/vg00/lvol9
reserve - 12399 -12399
memory 14307 6352 7955 44%
total 34403 18751 15652 55% - 0 -

[HPquestion]

As these are part of SWAP, can I ignore the
"core dump" stuff while doing make_tape_recovery backup? If not, how can I fix this? Thanks for any help on this...

[HPquestion]

I meant lvol2 and lvol9 are both part of SWAP...How can I fix the ignite (make_tape_recovery) backup...Thanks!

[HPquestion]

As these are swap space and there are no real file system on it, can I just ignore core dump error (seems like root case is fetyp check only). Please help. Thanks!

[HPquestion]

Dear all,I am looking forward to any help or suggestion on this...Thanks!

[Mridul Shrivastava]

Refer following threads and check the patches installed on the system:


http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1246502
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1173451
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1112641
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1109369