Path: g2news2.google.com!news4.google.com!feeder.news-service.com!85.214.198.2.MISMATCH!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: tristram.sc...@ntlworld.com (Tristram Scott)
Newsgroups: comp.sys.sun.admin
Subject: Re: st.conf for Quantum DAT 160
Date: Mon, 28 Mar 2011 12:08:36 +0000 (UTC)
Organization: A noiseless patient Spider
Lines: 53
Sender:  <trist...@cow.quantmodels.co.uk>
Message-ID: <impto4$7k3$1@dont-email.me>
References: <imabvn$bpt$1@news.eternal-september.org> <LIL19L.LL5@campus-news-reading.utoronto.ca> <imhj8c$t1g$1@dont-email.me> <LIM8y2.6L0@campus-news-reading.utoronto.ca>
Injection-Date: Mon, 28 Mar 2011 12:08:36 +0000 (UTC)
Injection-Info: mx03.eternal-september.org; posting-host="EhauM853eWZx9oG5SB2xew";
	logging-data="7811"; mail-complaints-to="ab...@eternal-september.org";	posting-account="U2FsdGVkX18XRzrlpUQ23R802hUdAYAefXwzZBZDkxE="
User-Agent: tin/1.9.5-20091224 ("Lochruan") (UNIX) (SunOS/5.10 (i86pc))
Cancel-Lock: sha1:0kzND3Zcb0bgLHNZtEk3UdPvn2k=

Oscar del Rio <del...@mie.utoronto.ca> wrote:
> On 03/25/11 04:20 AM, Tristram Scott wrote:
>> Oscar del Rio<del...@mie.utoronto.ca>  wrote:
>>> On 03/22/11 10:33 AM, Tristram Scott wrote:
>>>> I am looking for a definitive st.conf entry for the Quantum DAT 160 tape
>>>> drive.  Does anyone have a pointer to this?  I am using the following:
>>>>
>>>> "QUANTUM DAT   DAT160-00", "QUANTUM DAT   DAT160-00", "CFGQUANTUMDATDAT16000";
>>>> CFGQUANTUMDATDAT16000 = 2,0x34,0,0x18659,4,0x48,0x48,0x48, \
>>>> 0x48,3,120,300,600,1200,600,600,18000;
>>>
>>> Is "QUANTUM DAT   DAT160-00" the exact vendor inquiry string of the
>>> drive? If not, the st driver might be ignoring that entry.
>>
>> Yes, cut and pasted from the mt config output when the drive was first
>> connected (and reported as unknown, as per mt(1).
> 
> I would double check by changing the "pretty print" field and checking 
> that mt displays the string you specify when querying the drive.
> 
> Otherwise, the entry you have is similar, although not identical, to the 
> HP DAT-160 coded in the st driver. Check the (open)solaris st_conf.c 
> source code.
> 
> http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common
> /io/scsi/targets/st_conf.c

Thanks for the various ideas.  I did change the pretty print field to
confirm that it was picking up my entry. 

"QUANTUM DAT   DAT160-00", "QUANTUM DAT X DAT160-00", "CFGQUANTUMDATDAT16000";
CFGQUANTUMDATDAT16000 = 2,0x34,0,0x18619,4,0x48,0x48,0x48,0x48,3, \
120,300,600,1200,600,600,20000;

I have changed the name, adding the X, and also changed the values 0x18659
to 0x18619, and the last timeout from 18000 to 20000.

I did the reboot -- -r, and then mt config reports this:

chicken 1% mt config
"QUANTUM DAT   DAT160-00", "QUANTUM DAT X DAT160-00", "CFGQUANTUMDATXDAT16000";
CFGQUANTUMDATXDAT16000 = 2,0x34,0,0x18659,4,0x48,0x48,0x48,0x48,3,120,300,
600,1200,600,600,20000;

So it is picking up the new entry, including the moidified timeout value,
but the hex value for the flags is reverting back to 0x18659.

I am not sure what is happening there.  Perhaps there was some negotiation
between Solaris and the drive?

-- 
Dr Tristram J. Scott               
Energy Consultant