Networker

[Networker] Solaris 9, Exabyte M2, and ST_BUFFERED_WRITES

2004-03-02 16:22:50
Subject: [Networker] Solaris 9, Exabyte M2, and ST_BUFFERED_WRITES
From: Matthew Huff <mhuff AT OX DOT COM>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Tue, 2 Mar 2004 16:22:30 -0500
Exabyte and Sun give these settings for st.conf for a Exabyte M2 drive:

tape-config-list=
"EXABYTE  Mammoth2",       "Exabyte Mammoth2",
"EXB-M2";

EXB-M2         = 1, 0x35,    0, 0x1de39, 1, 0x28, 0;

However, when you rem_mod st, add_mod st to reload the st driver, the
console complains of:

Mar  1 12:18:55 regulus scsi: [ID 193665 kern.info] st72 at qus0: target
2 lun 0 Mar  1 12:18:55 regulus genunix: [ID 936769 kern.info] st72 is
/pci@6,4000/pci@2/scsi@4/st@2,0 Mar  1 12:18:56 regulus scsi: [ID 107833
kern.notice] /pci@6,4000/pci@2/scsi@5/st@3,0 (st80):
Mar  1 12:18:56 regulus         EXB-M2 options value invalid bits set:
0x4000

Looking up in /usr/include/sys/scsi/targets/stdef.h, 0x4000 maps to:

#define ST_BUFFERED_WRITES      0x4000  /* The data is buffered in the
*/
                                        /* driver and pre-acked to the
*/
                                        /* application
*/

Removing this bit and using:

EXB-M2         = 1, 0x35,    0, 0x19e39, 1, 0x28,0; 

appears to work.

Anyone have any idea what this implication of not using
ST_BUFFERED_WRITES with M2 drives?

----
Matthew Huff           | One Manhattanville Rd
Director of Operations | Purchase, NY 10577
OTA LLC                | Phone: 914-460-4039 
http://www.otaotr.com  | Fax:   914-460-4139    

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

<Prev in Thread] Current Thread [Next in Thread>