> Well here's the word on st.conf for my DLT7K from Veritas tech support on
> Sol v2.6.
> 
> ----------Original Message-------------
> in /kernel/drv/st.conf
>  
> Uncomment the line tape-config-list
>  
> Uncomment the line in the second 'paragraph'-
> # "QUANTUM DLT7000",      "Quantum DLT7000", "DLT7k-data"; <--note the
> semicolon at end of line
>  
> Uncomment and edit the 3rd 'paragraph'
> #DLT7k-data =  1,0x38,0,0x1D639,4,0x82,0x83,0x84,0x85,2;
> DLT7k-data = 1,0x38,0,0x3D639,4,0x82,0x83,0x84,0x85,3;

That's pretty interesting....  I only see two changes in the line.

The end changes from 2 to 3, so the unspecified device (like /dev/rmt/0)
changes from compressed 20/40 to uncompressed 35/70.  If you're
specifying the device (like /dev/rmt/0un or /dev/rmt/0cn), then that
figure is irrelevant.

The other change is to add the 0x20000 bit to the options field.  Here's
how that apparantly translates..

     ST_NO_RESERVE_RELEASE                  0x20000
[....]
     ST_NO_RESERVE_RELEASE
           The ST_NO_RESERVE_RELEASE flag  disables  the  use  of
           reserve on open and release on close. If an attempt to
           use a ioctl of MTRESERVE or MTRELEASE on a drive  with
           this  flag  set,  it  will  return  an error of ENOTTY
           (inappropriate ioctl for device).

My guess is that this only has implications for reserve/release use
under SSO, and if it's just a single host talking to the drive, there's
no difference.

But I'm not sure why they recommend that it be disabled.  

-- 
Darren Dunham                                           ddunham AT taos DOT com
Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >