Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System Purpose 5 Scope 5 Conventions Used in This Guide 5 Reference Documents 6 Setting Up Communication with the Tape Drives 7 Before Installing the Tape Drive..............................................................................7 Installing the Tape Drive ..........................................................................................8 Verifying the st Module is Loaded ...................................
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System Document 6464215-01 Rev. B January 2006 Accessing Devices Using /dev/st* Device Nodes 11 Generating a List of Device Files ...........................................................................11 Reviewing the List of Device Files ........................................................................11 What To Do if a Device Node is Missing .............................................................
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System Document 6464215-01 Rev. B January 2006 Appendix B – Linux Reference Documentation 25 Appendix C – Sample stinit.def Definitions File 26 Recommendations ...................................................................................................26 Sample File................................................................................................................
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System Document 6464215-01 Rev. B January 2006 Made in the USA. Quantum Corporation provides this publication “as is” without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability or fitness for a particular purpose. Quantum Corporation may revise this publication from time to time without notice. COPYRIGHT STATEMENT © Copyright 2006 by Quantum Corporation.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Purpose 0 This document provides instructions for integrating a Quantum® DLTtape® drive, a Super DLTtape™ drive, a DLT VS tape drive, an LTO tape drive, or a DAT tape drive into Red Hat® Linux, Novell® SuSE® Linux, or other Linux operating system. Scope 0 This document is intended for users who have a general understanding of Linux operating systems.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Item Example Meaning “0” in an st file name st0 Represents the device number. * (asterisk) mt-st* In actual practice, this numeric character may be any number from 0 to 31 depending on the node. See Identifying Device Nodes on page 14 for more information. The asterisk is a placeholder representing the rest of the file name.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 If you do not have the correct product manual, you can view and download it from the Quantum Web site at: http://www.quantum.com/ServiceandSupport/ SoftwareandDocumentationDownloads/Index.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Installing the Tape Drive 0 To install the tape drive, follow these steps: 1 Shut down your workstation or server and remove AC power from the system. 2 Follow the instructions in your tape drive’s product manual to install the tape drive and set the SCSI ID. Verifying the st Module is Loaded 0 st is the tape device driver for Linux.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Verifying Communication with the Tape Drives 0 You must ensure the st driver sees the all the tape devices. If you have added a tape device, you must verify that the st driver sees the new device. You do this by displaying and reviewing the kernel initialization information which contains st driver initialization and attachment of SCSI tape devices.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Identifying the Tape Devices 0 You can identify the tape device by looking at the values listed for “channel” (PCI Bus), “id” (SCSI ID), and “lun” (lun is always “0” for standalone configurations). If you have more than one tape device, you should see similar lines of output for each device.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Vendor: SEAGATE Model: ST336607LC Rev: DS04 Type: Direct-Access ANSI SCSI revision: 03 Host: scsi1 Channel: 00 Id: 06 Lun: 00 Vendor: DELL Model: 1x6 U2W SCSI BP Rev: 5.39 Type: Processor ANSI SCSI revision: 02 Host: scsi2 Channel: 00 Id: 04 Lun: 00 Vendor: NEC Model: CD-ROM DRIVE:466 Rev: 1.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 You should see a block of four listings for each device. The list will look similar to the following: For this type of device... The list of /dev device files will look similar to...
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Interpreting the Device Node File Listing 0 The following table explains each part of the displayed device node listing shown in Reviewing the List of Device Files on page 11. Column Text Format Description First column crw-rw---- These ten characters describe access type and permissions.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Column Text Format Description Sixth column Mmm DD YYYY Date. Not applicable. Seventh column, section heading (n)stna Device Node Description. This is also the actual file name. n represents (n)st identifies the device node as either auto-rewind or no-rewind as a numeric character; a represents an alpha character.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Identifying Device Modes 0 Each node has four modes. Both the auto-rewind and no-rewind functions use the same modes. Mode Auto-Rewind Node (example)a No-Rewind Node (example) Alpha Character Identification 1 st0 nst0 no character 2 st0l nst0l lowercase l 3 st0m nst0m lowercase m 4 st0a nst0a lowercase a a. The “0” in this table is an example representing the device.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Creating Auto-Rewind Device Nodes 0 Creating No-Rewind Device Nodes 0 Use the mknod commands as shown in the following table to create autorewind device nodes. The table shows only the first two tape devices. You can have up to 32 tape devices per mode. For instructions on numbering more than two, see Creating Device Nodes.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 mt-st Linux RPM Package 0 The mt-st Linux Red Hat Package Manager (RPM) package consists of the following tools: • mt tape device manager (see mtx Tape Library Tool on page 20) • stinit tape configuration utility (see mt Tape Device Tool) In order to use the package, you must ensure that mt-st is installed.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 stinit and stinit.def 0 stinit automatically initializes SCSI tape drive modes at system startup or reboot by sending ioctl commands to the drive. The commands are defined in the stinit.def definitions text file. The text file is indexed using the inquiry data returned by the drive (manufacturer, device, and revision).
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 mode1 blocksize=0 compression=1 mode2 blocksize=1024 compression=1 mode3 blocksize=0 compression 0 mode4 blocksize = 1024 compression 0 } Identifying Tape DevicesandParameters0 You identify tape devices and parameters using keywords. The keywords correspond to the data returned by the tape device in response to a SCSI INQUIRY command.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Keyword Description block[size]=value The tape block size can be set to value bytes. Quantum recommends using the default block[size] = 0, signifying variable block mode. comp[ression]= value Compression of the data by the drive is enabled if value does not equal zero. Note that the tape driver cannot enable compression for all drives that can compress data.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Installing mtx 0 mtx is typically included on your Linux installation CD-ROMs (except for RHEL3.0). To install mtx, execute the following command: # rpm -ivh mtx* where the asterisk represents the remaining portion of the file name (in this case, it is the version number). For a detailed description of these access modes, refer to the appropriate product manual for your DLTtape mini-library.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Appendix A – Tape Drive and Cartridge Compatibility 0 This section provides information about tape cartridge and tape drive compatibility. Use these tables to determine which cartridges to use in your tape drive.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Tape Drive and Cartridge Compatibility – SDLT 0 Drive Type SDLT 220 SDLT 320 SDLT 600 DLTtape IV (CompacTape IV) 20/40 GB (read only) 35/70 GB (read only) 40/80 GB (read only) 20/40 GB (read only) 35/70 GB (read only) 40/80 GB (read only) N/A Super DLTtape I 110/220 GB 110/220 GB 160/320 GB Super DLTtape II N/A N/A 300/600 GB DLTtape VS1 N/A N/A 80/160 GB (read only) Cleaning Ta
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Tape Drive and Cartridge Compatibility – LTO 0 Drive Type Tape Cartridge Ultrium 1 Ultrium 2 Ultrium 3 Ultrium Cleaning Tape LTO-1 LTO-2 LTO-3 100/200 100/200 (read only) 100/200 (read only) N/A 200/400 200/400 (read only) N/A N/A 400/800 20 uses 20 uses 20 uses Tape Drive and Cartridge Compatibility – DDS/DAT 0 Drive Type Tape Cartridge DDS3 DDS4/SP40 DAT 72 DDS2 4/8 4/8
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Appendix B – Linux Reference Documentation 0 For further information about the topics discussed in this guide, refer to the following documentation: • stinit(8) man page • /usr/share/doc/mt-st-/stinit.def.examples • st(4) man page • dmesg(8) man page • /usr/src/linux-/Documentation/devices.txt • /usr/src/linux-/drivers/scsi/README.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Appendix C – Sample stinit.def Definitions File 0 This section provides a sample stinit.def definitions file. You must set up your stinit.def file if you have not done so already. Recommendations 0 This sample contains Quantum’s recommendations for setting up your stinit.def file. You may use the information provided here (you can copy and paste the information directly into your stinit.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 # 0x92 160.0 GB compression off # 0x93 320.0 GB compression on # QUANTUM SDLT220 # 0x48 100.0 GB # 0x90 100.0 GB compression off # 0x91 200.0 GB compression on # QUANTUM DLT8000 # 0x41 40.0 GB # 0x88 40.0 GB compression off # 0x89 80.0 GB compression on # CERTANCE ULTRIUM 3 # 0x44 400.0 GB # CERTANCE ULTRIUM 2 # 0x42 200.0 GB # CERTANCE ULTRIUM # 0x40 100.0 GB # CERTANCE DAT72 # 0x47 36.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 # 225 = /dev/nst1a Second SCSI tape, mode 3, no rewind # Global Keywords and Values drive-buffering=1 #scsi2logical=1 no-wait=0 buffering=0 async-writes=0 read-ahead=1 two-fms=0 auto-lock=0 fast-eom=1 can-bsr=1 noblklimits=0 # can-partitions=0 # QUANTUM SDLT600 manufacturer=QUANTUM model="SDLT600" { timeout=3600 # 1 hour timeout long-timeout=14400# 4 hour long timeout can-partitions=0 mode1 blocks
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 mode4 blocksize=0 density=0x1B compression=0 # DLT7000 density, compression off } # CERTANCE ULTRIUM 3 manufacturer=CERTANCE model="ULTRIUM 3" { timeout=800 long-timeout=14400 can-partitions=0 mode1 blocksize=0 density=0x44 compression=1 # ULTRIUM 3 density, compression on mode2 blocksize=0 density=0x44 compression=0 # ULTRIUM 3 density, compression off mode3 blocksize=0 density=0x42 compression=1
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 # QUANTUM DLT VS160 manufacturer=QUANTUM model="DLT VS160" { timeout=3600 long-timeout=14400 can-partitions=0 mode1 blocksize=0 density=0x50 compression=1 # VS160 density, compression on mode2 blocksize=0 density=0x50 compression=0 # VS160 density, compression off mode3 blocksize=0 density=0x40 compression=1 # VS80 density, compression on mode4 blocksize=0 density=0x40 compression=0 # VS80 density
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Appendix D – Troubleshooting 0 This section covers common errors. Problem Explanation Fix You receive a nonrecoverable error that looks similar to this after performing the tar command: The tape device has a blocksize set to a parameter value other than 0. Use mt to set the blocksize to 0 so the tape drive can operate in variable blocksize mode.
Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System 6464215-01, Rev B January 2006 Problem Explanation Fix The st driver does not see all attached tape devices. The connector cable may be too long. Verify that the connector cable length does not exceed the specifications listed in your product manual. Your SCSI bus may not be terminated properly. Ensure the SCSI bus is terminated properly (see your product manual for instructions).
