From markcarl@sac.sfbay.sun.com Tue Oct 23 10:41:47 2007 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9NHflQk014985 for ; Tue, 23 Oct 2007 10:41:47 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l9NHcHXe036718; Tue, 23 Oct 2007 11:38:19 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JQD00M05KZUB900@nwk-avmta-1.sfbay.Sun.COM>; Tue, 23 Oct 2007 10:38:18 -0700 (PDT) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQD0019WKZUABF0@nwk-avmta-1.sfbay.Sun.COM>; Tue, 23 Oct 2007 10:38:18 -0700 (PDT) Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id l9NHcIc4060306; Tue, 23 Oct 2007 10:38:18 -0700 (PDT) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9NHfhvA014980; Tue, 23 Oct 2007 10:41:43 -0700 (PDT) Received: (from markcarl@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id l9NHfhmc014976; Tue, 23 Oct 2007 10:41:43 -0700 (PDT) Date: Tue, 23 Oct 2007 10:41:43 -0700 (PDT) From: Mark Carlson Subject: Tape Self Identification [PSARC/2007/613 Self Review] To: PSARC-ext@Sun.COM Message-id: <200710231741.l9NHfhmc014976@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 Status: RO Content-Length: 4939 Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI This information is Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Tape Self Identification 1.2. Name of Document Author/Supplier: Author: Larry Liu 1.3 Date of This Document: 23 October, 2007 4. Technical Description Problem ----------- Today in Solaris, there are two methods to support a tape drive: adding entries in st.conf, or adding entries in st_conf.c. Both of them are static mechanisms and cost tape users or developers time to figure out what the configuration data is. To support a new tape drive, the developer needs to refer to the manual, find the configuration data, add a static entry in st_conf.c, test, then integrate it into solaris. This takes at least 2 months. Sometimes, the official tape reference manual is not available before it's RR date. So there is no way for us to find out what the configuration data should be. This influences the Solaris' official support for the tape drives and influences Sun's revenue. Solution ------------ We propose to let the st driver query the configuration from tape drives if there is no static entry in st.conf and st_conf.c. By sending SCSI-3 commands, some of which are optional, during attach time, the tape drives which support those commands are automatically configured. There are four methods to configure a tape drive. 1. add entry in st.conf 2. add entry in st_conf.c 3. tape self identification 4. default st driver tries to configure the tape device in order proceeding from method 1 to method 4 and will finish the configuration when the first of these methods completes successfully. The default configuration is always available. Querying the configuration from a tape drive is performed only after failing to read the configuration properties in st.conf and st_conf.c. So this method has no influence on the tape drives SUN already supports and customers can still add their own configuration data in st.conf which will override entries in st_conf.c and avoid querying the configuration from the tape drive. Interface Binding ------------------- This change imports the following interfaces between operating system and SCSI tape devices. _______________________________________________________________ | Interface Name | Proposed Stability | Specified in What | | | Classification | document | |___________________|______________________|____________________| | | | | | REPORT DENSITT | Committed | ssc3r03c, page 102 | | SUPPORT | | | | | | | | | | | | REPORT SUPPORTED | Committed | spc4r06, page 229 | | OPERATION CODES | | With Command | | | | timeouts descriptor| | | | in spc4r06, | | | | page 234 | |___________________|______________________|____________________| Man page of changes ---------------------------------- This man page will be integrated into st(7D) Write Operation Writing from the beginning of tape is performed in the user-specified format. The original tape format is used for appending onto previously written tapes. Tape Configuration | The st tape driver has a built-in configuration table for most | Sun supported tape drives. For those tape drives that are not | in the table, st driver tries to read the configuration from a | tape drive through optional SCSI-3 commands. To support the | addition of third party tape devices which are either not in | the built-in configuration table or not able to report their | configuration, device information can be supplied in st.conf | as global properties that apply to each node, or as properties | that are applicable to one node only. By supplying the | information in st.conf, the built-in configuration is overridden | and st driver will not query the configuration from tape drives. | The st driver looks for the property called "tape-config-list." | The value of this property is a list of triplets, where each | triplet consists of three strings. The formal syntax is: tape-config-list = [, *]; 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: Automatic 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: Automatic 6.6. ARC Exposure: open From carlsonj@phorcys.east.sun.com Tue Oct 23 10:53:49 2007 Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9NHrmTZ015314 for ; Tue, 23 Oct 2007 10:53:49 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l9NHoEYQ005811 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@Sun.Com>; Wed, 24 Oct 2007 01:50:20 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JQD0001RLJVL100@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Tue, 23 Oct 2007 10:50:19 -0700 (PDT) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQD0011JLJTALF0@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Tue, 23 Oct 2007 10:50:18 -0700 (PDT) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l9NHnmhS019403; Tue, 23 Oct 2007 13:49:48 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l9NHnmuP019400; Tue, 23 Oct 2007 13:49:48 -0400 (EDT) Date: Tue, 23 Oct 2007 13:49:48 -0400 From: James Carlson Subject: Re: Tape Self Identification [PSARC/2007/613 Self Review] In-reply-to: <200710231741.l9NHfhmc014976@sac.sfbay.sun.com> To: Mark Carlson Cc: PSARC-ext@sun.com Message-id: <18206.13372.667661.414601@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200710231741.l9NHfhmc014976@sac.sfbay.sun.com> Status: RO Content-Length: 608 Mark Carlson writes: > Today in Solaris, there are two methods to support a tape drive: > adding entries in st.conf, or adding entries in st_conf.c. What's the release binding? Is this new feature equivalent to configuring the device using the existing "mt config" command? If so, then perhaps an update to mt(1) to tell users that they needn't do this anymore would be helpful. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From Grant.Zhang@sun.com Tue Oct 23 17:02:02 2007 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9O022Qf026902 for ; Tue, 23 Oct 2007 17:02:02 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l9NNwTcU027453 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 24 Oct 2007 00:58:33 +0100 (BST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JQE005052LKRE00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 23 Oct 2007 17:58:32 -0600 (MDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQE00JBT2LJ7T70@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 23 Oct 2007 17:58:32 -0600 (MDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l9NNwULY010421 for ; Tue, 23 Oct 2007 23:58:30 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JQE00K012E73N00@mail-apac.sun.com> (original mail from Grant.Zhang@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 24 Oct 2007 07:58:30 +0800 (SGT) Received: from [129.150.144.10] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JQE00HFU2LHYHUP@mail-apac.sun.com>; Wed, 24 Oct 2007 07:58:30 +0800 (SGT) Date: Wed, 24 Oct 2007 07:58:29 +0800 From: Grant Zhang Subject: Re: Tape Self Identification [PSARC/2007/613 Self Review] In-reply-to: <18206.13372.667661.414601@gargle.gargle.HOWL> Sender: Grant.Zhang@sun.com To: James Carlson Cc: Mark Carlson , psarc-ext@sun.com Message-id: <471E8AA5.2000309@sun.com> Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 8BIT X-PMX-Version: 5.2.0.264296 References: <200710231741.l9NHfhmc014976@sac.sfbay.sun.com> <18206.13372.667661.414601@gargle.gargle.HOWL> User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) Status: RO Content-Length: 864 Hi James, This case seeks patch binding. This new feature enables st(7D) to retrieve configuration data directly from the tape device, if no matching entry is found in st.conf or st's internal configuration table(st_conf.c). The existing "mt config" only reports the tape configuration data the st driver currently is using. The case does not intend to change "mt config" to do actual configuration. Thanks, Grant James Carlson 写道: > Mark Carlson writes: > >> Today in Solaris, there are two methods to support a tape drive: >> adding entries in st.conf, or adding entries in st_conf.c. >> > > What's the release binding? > > Is this new feature equivalent to configuring the device using the > existing "mt config" command? If so, then perhaps an update to mt(1) > to tell users that they needn't do this anymore would be helpful. > > From carlsonj@phorcys.east.sun.com Wed Oct 24 05:14:39 2007 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l9OCEdMW008378 for ; Wed, 24 Oct 2007 05:14:39 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l9OCB5iK028011; Wed, 24 Oct 2007 06:11:08 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JQF007030II7500@nwk-avmta-2.sfbay.sun.com>; Wed, 24 Oct 2007 05:11:06 -0700 (PDT) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JQF00FPF0IEWBE0@nwk-avmta-2.sfbay.sun.com>; Wed, 24 Oct 2007 05:11:03 -0700 (PDT) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l9OCAZ7v022631; Wed, 24 Oct 2007 08:10:35 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l9OCAZuA022628; Wed, 24 Oct 2007 08:10:35 -0400 (EDT) Date: Wed, 24 Oct 2007 08:10:35 -0400 From: James Carlson Subject: Re: Tape Self Identification [PSARC/2007/613 Self Review] In-reply-to: <471E8AA5.2000309@sun.com> To: Grant Zhang Cc: psarc-ext@sun.com, Mark Carlson Message-id: <18207.13883.73447.21755@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200710231741.l9NHfhmc014976@sac.sfbay.sun.com> <18206.13372.667661.414601@gargle.gargle.HOWL> <471E8AA5.2000309@sun.com> Status: RO Content-Length: 630 Grant Zhang writes: > This new feature enables st(7D) to retrieve configuration data directly > from the tape device, if no matching entry is found in st.conf or st's > internal configuration table(st_conf.c). The existing "mt config" only > reports the tape configuration data the st driver currently is using. > The case does not intend to change "mt config" to do actual configuration. OK; thanks. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677