Operating System - HP-UX
1836590 Members
1424 Online
110102 Solutions
New Discussion

Where to point make_tape_recovery to changed HW instance No.?

 
Ralph Grothe
Honored Contributor

Where to point make_tape_recovery to changed HW instance No.?

# tail /var/opt/ignite/recovery/latest/recovery.log
System Recovery Archive

* Checking Versions of Ignite-UX filesets
Hello,

partly for cosmetic reason, partly in hope to satisfy OmniBack I changed a couple of HW instance Nos. to make device files look the same on all cluster nodes.
I used the "ioinit -f" procedure in runlevel 1 to this end.
Although this worked as expected it haunted me back when I wanted to make_tape_recovery of the freshly configured cluster node.

It rightly complains about a tape device misnomer:


ERROR: Failed to open tape device /dev/rmt/0mn:No such device or address
(errno = 6).
ERROR: Check tape device failed.


======= 03/07/03 22:25:08 MET make_tape_recovery completed unsuccessfully


Hm, I modified hw.info to suite the new instance No.


# grep ext_bus /var/opt/ignite/local/hw.info
ext_bus: 0/0/1/0 3 c720 n/a SCSI_C895_Ultra_Wide_LVD
ext_bus: 0/0/2/0 1 c720 n/a SCSI_C87x_Ultra_Wide_Single-Ended
ext_bus: 0/0/2/1 2 c720 n/a SCSI_C87x_Ultra_Wide_Single-Ended

# ioscan -knfCtape
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 0 0/0/1/0.1.0 stape CLAIMED DEVICE HP C5683A
/dev/rmt/c3t1d0BEST /dev/rmt/c3t1d0DDS
/dev/rmt/c3t1d0BESTb /dev/rmt/c3t1d0DDSb
/dev/rmt/c3t1d0BESTn /dev/rmt/c3t1d0DDSn
/dev/rmt/c3t1d0BESTnb /dev/rmt/c3t1d0DDSnb


# ioscan -kfCext_bus -H 0/0/1
Class I H/W Path Driver S/W State H/W Type Description
=================================================================
ext_bus 3 0/0/1/0 c720 CLAIMED INTERFACE SCSI C895 Ultra Wide LVD

but it still croaks :-(

Who knows where instead to register the new tape device file to satisfy make_tape_recovery?

Rgds.

Ralph
Madness, thy name is system administration
7 REPLIES 7
Ralph Grothe
Honored Contributor

Re: Where to point make_tape_recovery to changed HW instance No.?

Oops, sorry for the clutter in the opening.

Looks I had a copy'n'paste synchronity loss here ;-)
Madness, thy name is system administration
James R. Ferguson
Acclaimed Contributor

Re: Where to point make_tape_recovery to changed HW instance No.?

Hi Ralph:

You can specify '-a /dev/rmt/c3t1d0BESTn' with your 'make_tape_recovery' command.

Regards!

...JRF...
Pete Randall
Outstanding Contributor

Re: Where to point make_tape_recovery to changed HW instance No.?

You could also create a device file for /dev/rmt/0mn and associate it with this path. See man mksf.

Pete

Pete
monasingh_1
Trusted Contributor

Re: Where to point make_tape_recovery to changed HW instance No.?

delete your existing tape device with rmsf -H command.
and then re-create using insf -H command

then check the device name for tape
then make_recovery -A -d /dev/rmt/Xmn

This should work....
monasingh_1
Trusted Contributor

Re: Where to point make_tape_recovery to changed HW instance No.?

for make_tape_recovery use -a option for tape device...
Ralph Grothe
Honored Contributor

Re: Where to point make_tape_recovery to changed HW instance No.?

Thank you all for your help.

Of course did I find out about the -a switch to feed make_tape_recovery with a preffered device.
But this wasn't the way I wanted it because I realized that my installation lacked the default tape device files.
The ordinary "insf -d stape -e" didn't create them for me.
It took quite some experimenting until I found out, by scrutiny of what lssf dumped on another box that had those files, viz.:

# lssf /dev/rmt/0m*
stape card instance 3 SCSI target 0 SCSI LUN 0 at&t best density available at ad
dress 0/0/2/1.0.0 /dev/rmt/0m
stape card instance 3 SCSI target 0 SCSI LUN 0 berkeley best density available a
t address 0/0/2/1.0.0 /dev/rmt/0mb
stape card instance 3 SCSI target 0 SCSI LUN 0 at&t no rewind best density avail
able at address 0/0/2/1.0.0 /dev/rmt/0mn
stape card instance 3 SCSI target 0 SCSI LUN 0 berkeley no rewind best density a
vailable at address 0/0/2/1.0.0 /dev/rmt/0mnb

that I needed to supply driver specific extra options when issuing the mksf command.

Finally that seemed to work:

# mksf -I 0 -d stape -H 0/0/1/0.1.0 -a -b BEST /dev/rmt/0m
# mksf -I 0 -d stape -H 0/0/1/0.1.0 -u -b BEST /dev/rmt/0mb
# mksf -I 0 -d stape -H 0/0/1/0.1.0 -n -a -b BEST /dev/rmt/0mn
# mksf -I 0 -d stape -H 0/0/1/0.1.0 -n -u -b BEST /dev/rmt/0mnb

# ioscan -knfdstape
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 0 0/0/1/0.1.0 stape CLAIMED DEVICE HP C5683A
/dev/rmt/0m /dev/rmt/c3t1d0BESTn
/dev/rmt/0mb /dev/rmt/c3t1d0BESTnb
/dev/rmt/0mn /dev/rmt/c3t1d0DDS
/dev/rmt/0mnb /dev/rmt/c3t1d0DDSb
/dev/rmt/c3t1d0BEST /dev/rmt/c3t1d0DDSn
/dev/rmt/c3t1d0BESTb /dev/rmt/c3t1d0DDSnb
# lssf /dev/rmt/0m*
stape card instance 3 SCSI target 1 SCSI LUN 0 at&t best density available at ad
dress 0/0/1/0.1.0 /dev/rmt/0m
stape card instance 3 SCSI target 1 SCSI LUN 0 berkeley best density available a
t address 0/0/1/0.1.0 /dev/rmt/0mb
stape card instance 3 SCSI target 1 SCSI LUN 0 at&t no rewind best density avail
able at address 0/0/1/0.1.0 /dev/rmt/0mn
stape card instance 3 SCSI target 1 SCSI LUN 0 berkeley no rewind best density a
vailable at address 0/0/1/0.1.0 /dev/rmt/0mnb


Madness, thy name is system administration
Pete Randall
Outstanding Contributor

Re: Where to point make_tape_recovery to changed HW instance No.?

Ralph,

I'm sorry I couldn't have spelled it out more clearly for you. I've got the whole procedure written out step by step at work, but I answered from home and wasn't about to trust my crummy memory.

So, you're all set now?

Pete

Pete