Right, but I have seen entries commented out in sd.conf keep the drive from
being seen. for instance:
# in sd.conf, standard entry for target3, lun0 commented out
#name="sd" class="scsi"
target=3 lun=0;
# Entry looked like this in st.conf
name="st" class="scsi"
target=3 lun=0;
and the tape was never seen so we added an entry that looked like this in
sd.conf:
name="sd" class="scsi" target=3 hba="fcaw3" lun=0;
and the tape drive was seen just fine.
--Buddy
-----Original Message-----
From: anthony.guzzi AT storability DOT com
[mailto:anthony.guzzi AT storability DOT com]
Sent: Wednesday, October 03, 2001 7:43 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Cc: Buddy.Lumpkin AT nordstrom DOT com
Subject: [Veritas-bu] Re: sd.conf entries affecting what tape drives are
seen
Buddy,
As far as the JNI driver using the information (I wouldn't exactly say
'parse') in the 'sd.conf' and 'st.conf', yes it does. I also appears to
use any binding information in the 'sg.conf' file (the Generic SCSI driver
config file). I'm going to hazard a guess that the JNI driver is using
any binding information it finds in any driver in the 'scsi' class (to
which the 'st', 'sd', and 'sg' drivers belong). Since the disks need to
be accessed first during a boot, I'm guessing the 'sd' info is first in
line with the 'st' and 'sg' info behind it. I'm also guessing that the
driver uses the info in the order it sees it and that order is the same as
the order the OS loaded the config info.
The 'technote' supplied with the driver from JNI deals mostly with disks
(almost all the examples are for the 'sd' driver). Tapes really aren't
addressed. As for the behavior as it pertains to the information in the
'st.conf' and 'sd.conf' files, what I reported all comes from a series of
tests I had to run on the driver in order to "qualify" it for us in
installation we support. As odd as it may sound, with default binding
enabled (i.e. the 'def_hba_binding' set to "fcaw*") , you can bind tape
drives by via lines in the 'sd.conf' (yes, "SCSI Disk" config file) that
begin 'name="sd"' just as long the 'hba=' and 'wwpn=' (or 'wwnn=', if you
use node name) contain the correct information for the tape drive. This
stuck me a very odd but it is how the driver behaves. No matter what I
put into the 'st.conf' (SCSI Tape) file, I couldn't get any of the
bindings in there to take effect. I've confirmed this in our lab and
it's easily reproducible.
Welcome to the world of persistent binding with JNI drivers.
-- Tony Guzzi
Sr. Solutions Engineer, AssuredRestore team
Storability, Inc.
From: "Lumpkin, Buddy" <Buddy.Lumpkin AT nordstrom DOT com>
To: "'Mike Andres'" <mike_andres AT cnt DOT com>,
"'Steve Hastings'"
<stevehas AT us.ibm DOT com>,
"Lumpkin, Buddy" <Buddy.Lumpkin AT nordstrom DOT com>,
veritas-bu AT mailman.eng.auburn DOT edu,
"'veritas-vx AT mailman.eng.auburn DOT edu'"
<veritas-vx AT mailman.eng.auburn DOT edu>,
emc-l AT lists.blinky-lights DOT org
Date: Tue, 2 Oct 2001 14:44:19 -0600
Subject: [Veritas-bu] RE: [Veritas-vx] sd.conf entries affecting what tape
drives are seen (GURU's and HACKERS please read!)
Ok, so you guys are saying that you think they sd.conf and st.conf files
are parsed by the JNI driver? That's an interesting way of looking at it.
Can you point me to a document that outlines this behavior or is this just
the way that you would guess it behaves?
--Buddy
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
