This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C36295.1293EF80
Content-Type: text/plain
Sun will tell your that the DLT drives are supported as-is and not required
in the st.conf file. Your experience may be proof of that statement. My
problem children are my Ultrium LTO's.
-M
-----Original Message-----
From: Steven L. Sesar [mailto:ssesar AT mitre DOT org]
Sent: Thursday, August 14, 2003 12:36 PM
To: David Chapa
Cc: Donaldson, Mark; Veritasbu (E-mail)
Subject: Re: [Veritas-bu] Mismatch between sgscan output & st.conf entry?
I don't think that it's read from st.conf.
I use SDLT220's all over, and have no entries in st.conf for them, as they
are unneccesary.
However, view my sgscan output:
/dev/sg/c0t20l0: Changer: "STK L700"
/dev/sg/c0t20l1: Tape (/dev/rmt/0): "QUANTUM SuperDLT1"
/dev/sg/c0t20l2: Tape (/dev/rmt/1): "QUANTUM SuperDLT1"
/dev/sg/c0t20l3: Tape (/dev/rmt/2): "QUANTUM SuperDLT1"
/dev/sg/c0t20l4: Tape (/dev/rmt/3): "QUANTUM SuperDLT1"
/dev/sg/c0t21l0: Tape (/dev/rmt/4): "QUANTUM SuperDLT1"
/dev/sg/c0t21l1: Tape (/dev/rmt/5): "QUANTUM SuperDLT1"
/dev/sg/c0t21l2: Tape (/dev/rmt/6): "QUANTUM SuperDLT1"
/dev/sg/c0t21l3: Tape (/dev/rmt/7): "QUANTUM SuperDLT1"
/dev/sg/c0t22l0: Changer: "STK L180"
/dev/sg/c0t22l1: Tape (/dev/rmt/8): "QUANTUM SuperDLT1"
/dev/sg/c0t22l2: Tape (/dev/rmt/9): "QUANTUM SuperDLT1"
/dev/sg/c0t22l3: Tape (/dev/rmt/10): "QUANTUM SuperDLT1"
/dev/sg/c0t23l0: Tape (/dev/rmt/12): "QUANTUM SuperDLT1"
/dev/sg/c0t23l1: Tape (/dev/rmt/13): "QUANTUM SuperDLT1"
/dev/sg/c1t22l4: Tape (/dev/rmt/11): "QUANTUM SuperDLT1"
David Chapa wrote:
Yes, that is the inquiry string that comes from the drive (or vendor
string).
-----Original Message-----
From: Donaldson, Mark [ mailto:Mark.Donaldson AT experianems DOT com
<mailto:Mark.Donaldson AT experianems DOT com> ]
Sent: Wednesday, August 13, 2003 11:51 AM
To: Veritasbu (E-mail)
Subject: [Veritas-bu] Mismatch between sgscan output & st.conf entry?
I've got this (potential) mismatch between my "sgscan tape" output & the
st.conf file (Solaris 8). If I udnerstand correctly, the name returned
in
the third field of sgscan for a tape should be the same as the first
field
of the st.conf "tape-config-list" entry for that device.
Can somebody confirm this?
If this is the case, it could be the root of some problems of mine. I
may
not be running an appropriate set of parameters for my LTO drives.
If this is not the case, what command should I be using to query the
drive
identification to compare against the st.conf file?
Advise anyone?
-M
Here's "sgscan tape":
/dev/sg/c1t3l1: (/dev/rmt/0): "HP Ultrium 1-SCSI"
<snip>
/dev/sg/c1t5l2: (/dev/rmt/8): "QUANTUM SuperDLT1"
Here's the relevant st.conf lines:
grep -v "^#" /kernel/drv/st.conf
tape-config-list=
"HP Ultrium", "HP Ultrium", "HP_LTO",
"QUANTUM SuperDLT1", "Quantum SDLT 220", "SDLT_220";
HP_LTO = 1,0x36,0,0x1d639,4,0x00,0x00,0x00,0x00,3;
SDLT_220 = 1,0x38,0,0x1d639,4,0x90,0x91,0x90,0x91,3;
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
<mailto:Veritas-bu AT mailman.eng.auburn DOT edu>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
<http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu>
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
<mailto:Veritas-bu AT mailman.eng.auburn DOT edu>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
<http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu>
--
===================================
Steven L. Sesar
Senior Operating Systems Programmer/Analyst
UNIX Application Services R10A
The MITRE Corporation
202 Burlington Road - KS101
Bedford, MA 01730
tel: (781) 271-7702
fax: (781) 271-2600
mobile: (617) 893-9635
email: ssesar AT mitre DOT org <mailto:ssesar AT mitre DOT org>
===================================
------_=_NextPart_001_01C36295.1293EF80
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<TITLE></TITLE>
<META content=3D"MSHTML 5.50.4926.2500" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV><SPAN class=3D605285018-14082003><FONT face=3DArial =
color=3D#0000ff size=3D2>Sun=20
will tell your that the DLT drives are supported as-is and not required =
in the=20
st.conf file. Your experience may be proof of that =
statement. My=20
problem children are my Ultrium LTO's.</FONT></SPAN></DIV>
<DIV><SPAN class=3D605285018-14082003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D605285018-14082003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>-M</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> Steven L. Sesar=20
[mailto:ssesar AT mitre DOT org]<BR><B>Sent:</B> Thursday, August 14, 2003 =
12:36=20
PM<BR><B>To:</B> David Chapa<BR><B>Cc:</B> Donaldson, Mark; Veritasbu =
(E-mail)<BR><B>Subject:</B> Re: [Veritas-bu] Mismatch between sgscan =
output=20
& st.conf entry?<BR><BR></FONT></DIV>I don't think that it's read =
from=20
st.conf.<BR><BR>I use SDLT220's all over, and have no entries in =
st.conf for=20
them, as they are unneccesary.<BR><BR>However, view my sgscan=20
output:<BR><BR>/dev/sg/c0t20l0: Changer: "STK =
L700"<BR>/dev/sg/c0t20l1: Tape (/dev/rmt/0): "QUANTUM SuperDLT1"=20
<BR>/dev/sg/c0t20l2: Tape (/dev/rmt/1): "QUANTUM SuperDLT1"=20
<BR>/dev/sg/c0t20l3: Tape (/dev/rmt/2): "QUANTUM SuperDLT1"=20
<BR>/dev/sg/c0t20l4: Tape (/dev/rmt/3): "QUANTUM SuperDLT1"=20
<BR>/dev/sg/c0t21l0: Tape (/dev/rmt/4): "QUANTUM SuperDLT1"=20
<BR>/dev/sg/c0t21l1: Tape (/dev/rmt/5): "QUANTUM SuperDLT1"=20
<BR>/dev/sg/c0t21l2: Tape (/dev/rmt/6): "QUANTUM SuperDLT1"=20
<BR>/dev/sg/c0t21l3: Tape (/dev/rmt/7): "QUANTUM SuperDLT1"=20
<BR>/dev/sg/c0t22l0: Changer: "STK =20
L180"<BR>/dev/sg/c0t22l1: Tape (/dev/rmt/8): "QUANTUM SuperDLT1"=20
<BR>/dev/sg/c0t22l2: Tape (/dev/rmt/9): "QUANTUM SuperDLT1"=20
<BR>/dev/sg/c0t22l3: Tape (/dev/rmt/10): "QUANTUM SuperDLT1"=20
<BR>/dev/sg/c0t23l0: Tape (/dev/rmt/12): "QUANTUM SuperDLT1"=20
<BR>/dev/sg/c0t23l1: Tape (/dev/rmt/13): "QUANTUM SuperDLT1"=20
<BR>/dev/sg/c1t22l4: Tape (/dev/rmt/11): "QUANTUM =
SuperDLT1"<BR><BR>David=20
Chapa wrote:<BR>
<BLOCKQUOTE =
cite=3D"mid96A586650E6357498A92FA40B70C677A016DAC AT mail01dn.adic DOT com"=20
type=3D"cite"><PRE wrap=3D"">Yes, that is the inquiry string that =
comes from the drive (or vendor
string).
-----Original Message-----
From: Donaldson, Mark [<A class=3Dmoz-txt-link-freetext =
href=3D"mailto:Mark.Donaldson AT experianems DOT com">mailto:Mark.Donaldson@exp=
erianems.com</A>]=20
Sent: Wednesday, August 13, 2003 11:51 AM
To: Veritasbu (E-mail)
Subject: [Veritas-bu] Mismatch between sgscan output & st.conf =
entry?
I've got this (potential) mismatch between my "sgscan tape" output =
& the
st.conf file (Solaris 8). If I udnerstand correctly, the name returned
in
the third field of sgscan for a tape should be the same as the first
field
of the st.conf "tape-config-list" entry for that device. =20
Can somebody confirm this?
If this is the case, it could be the root of some problems of mine. I
may
not be running an appropriate set of parameters for my LTO drives.
If this is not the case, what command should I be using to query the
drive
identification to compare against the st.conf file?
Advise anyone?
-M
Here's "sgscan tape":
/dev/sg/c1t3l1: (/dev/rmt/0): "HP Ultrium 1-SCSI"
<snip>
/dev/sg/c1t5l2: (/dev/rmt/8): "QUANTUM SuperDLT1"
Here's the relevant st.conf lines:
</PRE>
<BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">grep -v "^#" =
/kernel/drv/st.conf
</PRE></BLOCKQUOTE><PRE wrap=3D""><!---->
tape-config-list=3D
"HP Ultrium", "HP Ultrium", "HP_LTO",
"QUANTUM SuperDLT1", "Quantum SDLT 220", "SDLT_220";
HP_LTO =3D 1,0x36,0,0x1d639,4,0x00,0x00,0x00,0x00,3;
SDLT_220 =3D 1,0x38,0,0x1d639,4,0x90,0x91,0x90,0x91,3;
_______________________________________________
Veritas-bu maillist - <A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:Veritas-bu AT mailman.eng.auburn DOT edu">Veritas-bu AT mailman
DOT eng=
.auburn.edu</A>
<A class=3Dmoz-txt-link-freetext =
href=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu";>http:=
//mailman.eng.auburn.edu/mailman/listinfo/veritas-bu</A>
_______________________________________________
Veritas-bu maillist - <A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:Veritas-bu AT mailman.eng.auburn DOT edu">Veritas-bu AT mailman
DOT eng=
.auburn.edu</A>
<A class=3Dmoz-txt-link-freetext =
href=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu";>http:=
//mailman.eng.auburn.edu/mailman/listinfo/veritas-bu</A>
</PRE></BLOCKQUOTE><BR><BR><PRE class=3Dmoz-signature cols=3D"72">--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Steven L. Sesar
Senior Operating Systems Programmer/Analyst
UNIX Application Services R10A
The MITRE Corporation
202 Burlington Road - KS101
Bedford, MA 01730
tel: (781) 271-7702
fax: (781) 271-2600
mobile: (617) 893-9635
email: <A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:ssesar AT mitre DOT org">ssesar AT mitre DOT org</A>
=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</PRE></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C36295.1293EF80--
|
