Summary: DLT7000 Configuration (st.conf) and mt stat Behaviour in Solaris 8.0

Thanks for the few responses I received... The trick here is to closely
follow the man page of st.conf from Solaris 2.6 to 8,
/usr/include/sys/mtio.h and inputs from the vendor. The st(7d) man page
details what each device parameter means... the densities part you can get
from your device vendor..


However, with Solaris 8... I still could not find out what's causing 'mt
stats' to be at least 10 times slow as in Solaris  2.6. This is a problem
somewhat as device operations ie. loads and reloads are affected.  I've
already applied the latest Solaris 8 patches anddid some  search on
SunSolve but came out empty handed...


Thanks all.


Nelson



Original Message:
=============================
List:

I am a bit confused which st.conf device property setting (4th field) should
we be using in ou dynamically shared library comprising of Quantum DLT7000
drives in a Solaris 8 environment. The following are the configurations
suggested thus far:

SUN (via the st(7d) man pages of Solaris 8, not tested yet):
DLT7k-data	=	1,0x36,0,0x61D639,4,0x82,0x83,0x84,0x85,3;

A Tape Backup Specialist is suggesting this (tested but problems with
reservation...):
DLT7k-data	=	1,0x36,0,0x1D639,4,0x82,0x83,0x84,0x85,3;

Quantum Suggested - working in Solaris 2.6 (with st.conf patch...)
DLT7k-data	=	1,0x36,0,0x8639,4,0x82,0x83,0x84,0x85,3;

Also, mt stat seems to take longer (10x at least) to on Solaris 8... even on
locally attached DLT7000 (via SCSI).

Would anyone out there be in the same situation as we are... ? Any
recommendations  please?


Thanks.

Nelson Caparroso
IT Consultant