I have a few clients with the same scenario that you described and they were
told by a couple vendor support teams that the initialization string was
needed. Each one of them supplied a different string and each customer had
issues with drives going off line, tapes getting marked full 10MB into the
tape, etc...
Once the initialization strings were removed and they used the native driver
initialization the problems went away.
You do not need the st.conf entries if you have the latest st driver patch. By
saying that the LTO drives are supported natively essentially means that all
functionality has been turned on for the drive(s). The only reason to modify
the st.conf for LTO drives is to override functionality / characteristics. If
you put entries into the st.conf file for LTO drives you will override all
functionality that has been turned on. Don't do it unless you absolutly need
to (troubleshooting or specific needs). If you do need to create an st.conf
entry please refer to the man page on the ST driver.
http://docs.sun.com/app/docs/doc/816-0222/6m6nmlt2q?a=view
A crude way to find out what is supported by your current driver is to run:
> strings /kernel/drv/st | grep LTO
To answer you last question, no it really wouldn't matter if you used another
vendors st.conf entry. It does matter what chearacteristics have been enabled
though. Refer to the man page if you think you need one. Again, you don't
need one for any LTO-3 drive if the latest patch is installed.
Regards,
James Dean
Program Manager / Sr. Solutions Engineer
SANZ, Inc.
Vienna, VA
(443) 871-2404 Cell
jdean AT sanz DOT com
http://www.sanz.com
-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]On Behalf Of Paul Esson
Sent: Friday, January 13, 2006 4:18 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] IBM LTO-3 Drive on Solaris 8
Folks,
I am currently configuring an ADIC Scalar i2000 Library with 3 x IBM
LTO-3 drives on a Solaris 8 server running Networker 7.2.1. I have
applied Solaris patch 108725-22 which provides native support for the
IBM LTO-3 drive in the st driver. Do I still need to put a specific
entry for the drive in the st.conf file? I have read comments
suggesting that a) native support means there is no need for a st.conf
entry and b) native support will not guarantee the characteristics that
you might want from the drive. Comments please?
If any one is using the IBM LTO-3 with Solaris and had made a st.conf
entry could you share the details please? I have looked on the web and
found information on HP and Certance LTO-3 for Solaris but not IBM.
Would it matter if I used another vendor's LTO-3 settings?
Regards,
Paul Esson
Redstor Limited
Direct: +44 (0) 1224 595381
Mobile: +44 (0) 7766 906514
E-Mail: paul.esson AT redstor DOT com
Web: www.redstor.com
REDSTOR LIMITED
Torridon House
73-75 Regent Quay
Aberdeen
UK
AB11 5AR
Disclaimer:
The information included in this e-mail is of a confidential nature and
is intended only for the addressee. If you are not the intended
addressee, any disclosure, copying or distribution by you is prohibited
and may be unlawful. Disclosure to any party other than the addressee,
whether inadvertent or otherwise is not intended to waive privilege or
confidentiality.
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|