Veritas-bu

[Veritas-bu] Mismatch between sgscan output & st.conf entry?

2003-08-14 08:31:40
Subject: [Veritas-bu] Mismatch between sgscan output & st.conf entry?
From: Roy.Vosberg AT veritas DOT com (Roy Vosberg)
Date: Thu, 14 Aug 2003 07:31:40 -0500
You are missing some spaces.  The HP    Ultrium part must match exactly.  It
should look like this:

"HP      Ultrium",           "HP Ultrium",           "HP_LTO",


  (MAKE SURE THERE ARE NO TAB CHARACTERS INSIDE ANY QUOTES).  


Roy V.


-----Original Message-----
From: Donaldson, Mark [mailto:Mark.Donaldson AT experianems DOT com]
Sent: Wednesday, August 13, 2003 12:51 PM
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
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu