Sponsored Content
Full Discussion: Tape drive config issue
Operating Systems Solaris Tape drive config issue Post 302349593 by pfwhufc on Tuesday 1st of September 2009 10:16:19 AM
Old 09-01-2009
Additional Info

When I check the prtconf against the other cluster node, I see the following: -

node 1 (not working)
lpfc, instance #0
fp (driver not attached)
sd (driver not attached)
tape (driver not attached)

# modinfo | grep 'tape'
211 7b30c000 14e08 33 1 st (SCSI tape Driver 1.252)

node 2 (working)
lpfc, instance #0
fp (driver not attached)
sd (driver not attached)
tape (driver not attached)
st, instance #2
st, instance #3
st, instance #4
st, instance #5
st, instance #6
st, instance #7
st, instance #8
sd, instance #2 (driver not attached)
sd, instance #3 (driver not attached)
sd, instance #4 (driver not attached)
sd, instance #5 (driver not attached)
sd, instance #6 (driver not attached)
sd, instance #7 (driver not attached)
sd, instance #8 (driver not attached)
sd, instance #9 (driver not attached)
sd, instance #10 (driver not attached)
sd, instance #11 (driver not attached)
sd, instance #12 (driver not attached)
sd, instance #13 (driver not attached)
sd, instance #14 (driver not attached)
sd, instance #15 (driver not attached)
sd, instance #16 (driver not attached)
ses, instance #0 (driver not attached)
ses, instance #1 (driver not attached)
ses, instance #2 (driver not attached)
ses, instance #3 (driver not attached)
ses, instance #4 (driver not attached)
ses, instance #5 (driver not attached)
ses, instance #6 (driver not attached)
ses, instance #7 (driver not attached)
ses, instance #8 (driver not attached)
ses, instance #9 (driver not attached)
ses, instance #10 (driver not attached)
ses, instance #11 (driver not attached)
ses, instance #12 (driver not attached)
ses, instance #13 (driver not attached)
ses, instance #14 (driver not attached)
ses, instance #15 (driver not attached)

# modinfo | grep 'tape'
225 7b200000 14e08 33 1 st (SCSI tape Driver 1.252)

the /etc/devlink.tabs are identical, as are the /kernel/drv/st.confs.

lputil shows the persistent bindings as being okay.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Tape Drive on Unix 7.1.1

I am trying to install a tape drive on this system (Unix 7.1.1) where will I start? 1. Do I need to load the driver on the on board scsi? How? 2. Is there a driver for the tape drive itself? Things done: 1. Terminated the device on the controller board. (4 Replies)
Discussion started by: a4tech
4 Replies

2. Linux

Installing tape drive?

Hello. I have Redhat 8.0 on a laptop. Working good. I wanted to install the tape drive that is physically attached to it. The tape drive worked fine under Windows98SE. It's one of those parallel QIC-80 drives and I confirmed that it is supported by FTape. It appears that FTape might already... (0 Replies)
Discussion started by: RuralTurtle
0 Replies

3. UNIX for Dummies Questions & Answers

tape drive

Hi, I need to restore my tape backup, when I type "tape status" it gives; status : ready beginning-of-tape write-protected soft errors : 0 hard errors : 0 underruns : 3 but... (4 Replies)
Discussion started by: alisevA3
4 Replies

4. AIX

Tape Drive

I have tape drive in one Lpar. when i saw that time tape is in defined state. After that i deleted the tape drive using the rmdev -R command. Then fired the cfgmgr -v command. But I am not getting the tape drive. Now the drive is even not in defined state also. It is not shown the tape drive. How... (1 Reply)
Discussion started by: pernasivam
1 Replies

5. AIX

Tape drive defined

Hello everyone I have a problem with one of my drives in an aix box. The library is a 3583 and Aix is 5.3 TL9 The problem was that the fibre channel not work and I change the fibre but when I logging to the aix box I got this in the rmt3 lsdev | grep rmt rmt0 Available 03-08-00-6,0... (4 Replies)
Discussion started by: lo-lp-kl
4 Replies

6. Solaris

Help with tape drive

Hey folks, Linux admin here, forced to use Opensolaris to try to use ufsdump/ufsrestore to get some data of some old tapes. I've got Opensolaris 2009.06 on x86 and a Sony SDX-700V. As a "control" experiment, I booted the system with a Linux live CD and the tape drive worked perfectly. ... (2 Replies)
Discussion started by: eddy_sysad
2 Replies

7. HP-UX

TAPE drive

I have used ioscan -fnC tape and the system identified the tape drive. what is the command to show a listing of what is on the tape? I have used ls /dev/rmt/rmt0 to no avail. can anyone help? Thanks in advance (10 Replies)
Discussion started by: Randydog
10 Replies

8. SCO

Mounting Tape Drive

Sorry I posted it in wrong forum first. OK, I'm new to Unix (but an IT since DOS 6.2 era) Long story short I'm trying to help a friend who has failing Unix system which is perhaps 16 years old with SCO Openserver 3.4v4.2 with DDS90 Tape where they backup their data. I've setup a Dell Precision... (9 Replies)
Discussion started by: shunail
9 Replies
ddi_get_instance(9F)					   Kernel Functions for Drivers 				      ddi_get_instance(9F)

NAME
ddi_get_instance - get device instance number SYNOPSIS
#include <sys/ddi.h> #include <sys/sunddi.h> int ddi_get_instance(dev_info_t *dip); INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). PARAMETERS
dip Pointer to dev_info structure. DESCRIPTION
ddi_get_instance() returns the instance number of the device corresponding to dip. The system assigns an instance number to every device. Instance numbers for devices attached to the same driver are unique. This pro- vides a way for the system and the driver to uniquely identify one or more devices of the same type. The instance number is derived by the system from different properties for different device types in an implementation specific manner. Once an instance number has been assigned to a device, it will remain the same even across reconfigurations and reboots. Therefore, instance numbers seen by a driver may not appear to be in consecutive order. For example, if device foo0 has been assigned an instance number of 0 and device foo1 has been assigned an instance number of 1, if foo0 is removed, foo1 will continue to be associated with instance number 1 (even though foo1 is now the only device of its type on the system). RETURN VALUES
ddi_get_instance() returns the instance number of the device corresponding to dip. CONTEXT
ddi_get_instance()can be called from user or interrupt context. SEE ALSO
path_to_inst(4) Writing Device Drivers SunOS 5.10 20 Jul 1994 ddi_get_instance(9F)
All times are GMT -4. The time now is 09:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy