background image

Installing a DLT, SDLT, VS, LTO, or DAT Tape Drive Into a Linux Operating System

6464215-01, Rev B

January 2006

Obtaining Device Information Using /proc/scsi/scsi

10

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. 

What To Do if Device 
Information is Missing

0

If you do not see the information for every attached tape device, then the 

st

 

driver is not communicating with the missing device(s). Try the following 

solutions:
• Verify that the connector cable length does not exceed the specifications 

listed in your product manual. 

• Make sure the SCSI bus is terminated properly (see your product manual 

for instructions). 

• Ensure there are enough 

st

 tape device nodes for all your attached tape 

devices. If not, you will need to create more. See 

Creating Device Nodes

 

on page 15 and 

Creating No-Rewind Device Nodes

 on page 16.

Obtaining Device Information Using /proc/scsi/scsi

0

To obtain information about a specific tape drive, view the 

/proc/scsi/scsi

 file. 

What is the /proc File 
System?

0

The

 /proc

 file system is a map to the running kernel process. It displays a list of 

connected SCSI devices. It is not a disk-based file system and is dynamic to 

reflect the current boot-up information. 

Viewing /proc Files

0

The recommended method to view 

/proc 

files is to use the 

cat

 command piped 

( | ) with command 

more 

or

 less

. Execute the following command: 

# cat /proc/scsi/scsi | less

The output will look something like the following:

Attached devices:
Host: scsi0 Channel: 00 Id: 03 Lun: 00
  Vendor: QUANTUM  Model: SDLT320          Rev: 5252
  Type:   Sequential-Access                ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 03 Lun: 00

Caution:

Do NOT execute the 

cat

 command on the 

/proc/kcore 

file. This 

unique file contains a running image of the kernel’s memory at 

that particular moment. Executing the 

cat

 command on this 

file will render your terminal unusable. 

Summary of Contents for LTO 1U

Page 1: ...s 7 Before Installing the Tape Drive 7 Installing the Tape Drive 8 Verifying the st Module is Loaded 8 Verifying Communication with the Tape Drives 9 Displaying the Kernel Initialization Information 9 Reviewing the Kernel Initialization Information 9 Identifying the Tape Devices 10 What To Do if Device Information is Missing 10 Obtaining Device Information Using proc scsi scsi 10 What is the proc ...

Page 2: ...ing No Rewind Device Nodes 16 mt st Linux RPM Package 17 Verifying mt st is Installed 17 Installing mt st 17 mt Tape Device Tool 17 stinit and stinit def 18 Tape Device and Parameter Definitions 18 Identifying Tape Devices and Parameters 19 Common Tape Device Keywords 19 Common Parameter Keywords 19 mtx Tape Library Tool 20 Verifying mtx is Installed 20 Installing mtx 21 Appendix A Tape Drive and ...

Page 3: ...Drive Into a Linux Operating System Document 6464215 01 Rev B January 2006 Contents 3 Appendix B Linux Reference Documentation 25 Appendix C Sample stinit def Definitions File 26 Recommendations 26 Sample File 26 Appendix D Troubleshooting 31 ...

Page 4: ...ation from time to time without notice COPYRIGHT STATEMENT Copyright 2006 by Quantum Corporation All rights reserved Your right to copy this document is limited by copyright law Making copies or adaptations without prior written authorization of Quantum Corporation is prohibited by law and constitutes a punishable violation of the law TRADEMARK STATEMENT Quantum DLT DLTtape the Quantum logo and th...

Page 5: ...tem other than Red Hat or Novell SuSE If these instructions are not adequate refer to the Linux user guide for your system This document pertains to the following products Tape drives DLT 2000 DLT 2000XT DLT 4000 DLT 7000 DLT 8000 SDLT 220 SDLT 320 SDLT 600 DLT1 VS80 VS160 DLT V4 LTO 1 LTO 2 LTO 3 and DAT 72 Mini libraries DLT 2500 DLT 2500XT DLT 2700 DLT 2700XT DLT 4500 and DLT 4700 Conventions U...

Page 6: ...a placeholder representing the rest of the file name Product Manual Title Document Number DLT 2000 DLT 2500 DLT 2700 Cartridge Tape Subsystem Product Manual 81 109132 03 DLT 2000XT DLT 2500XT DLT 2700XT Product Manual 81 109253 03 DLT 4000 Product Manual 81 60043 04 DLT 7000 Product Manual 81 60000 06 DLT 8000 Product Manual 81 60118 04 SDLT 220 and SDLT 320 Product Manual 81 85002 01 SDLT 600 Pro...

Page 7: ...T 2000 DLT 2500 or DLT 2700 product make sure it uses version V10 or higher controller firmware If it does not go to http www quantum com am service_support downloads default htm to download V10 The suggested method to determine what version of firmware you are running is to view the SCSI HBA Bios at boot up 2 Make sure that you have the appropriate SCSI interface and cable for your tape drive 3 O...

Page 8: ...t odescription SCSI Tape Driver author Kai Makisara license GPL parm buffer_kbs int description Default driver buffer size KB 32 parm max_buffers int description Maximum number of buffer allocated at initialisation 4 parm max_sg_segs int description Maximum number of scatter gather segments to use 32 parm blocking_open int description Block in open if not ready an no O_NONBLOCK 0 Novell SuSE Linux...

Page 9: ...n 0 st0 Block limits 4 16777212 bytes st Version 20030406 bufsize 32768 max init bufs 4 s g segs 16 SuSE9 output looks similar to the following Attached scsi tape st0 at scsi0 channel 0 id 3 lun 0 st0 try direct i o yes alignment 512 B max page reachable by HBA 1048575 st Version 20040318 fixed bufsize 32768 s g segs 256 Method Instructions View st information during boot up At boot up Linux displ...

Page 10: ...ices If not you will need to create more See Creating Device Nodes on page 15 and Creating No Rewind Device Nodes on page 16 Obtaining Device Information Using proc scsi scsi 0 To obtain information about a specific tape drive view the proc scsi scsi file What is the proc File System 0 The proc file system is a map to the running kernel process It displays a list of connected SCSI devices It is no...

Page 11: ...del SDLT600 Rev 1A1A Type Sequential Access ANSI SCSI revision 04 Accessing Devices Using dev st Device Nodes 0 You can access most devices by using a corresponding special device file stored in the dev directory Each tape device corresponds to eight device nodes four auto rewind nodes and four no rewind nodes Generating a List of Device Files 0 You can generate a list of the dev directory device ...

Page 12: ... listings are not present in the dev directory you need to create them Use the mknod commands described in Creating Auto Rewind Device Nodes on page 16 and Creating No Rewind Device Nodes on page 16 Refer to the following documentation for detailed instructions Your Linux documentation st 4 man page mknod 1 man page For this type of device The list of dev device files will look similar to Auto rew...

Page 13: ...ermission is granted a hyphen indicates write permission is denied The third character of each set identifies execute permissions An x indicates execute permission is granted a hyphen indicates execute permission is denied In the example shown the device is sequential access The owner and group both have read write permission but do not have execute permission global users have no permissions Seco...

Page 14: ...ple n st0 Device Node Description This is also the actual file name n st identifies the device node as either auto rewind or no rewind as follows st identifies the device node as auto rewind See Creating Auto Rewind Device Nodes on page 16 for more information nst identifies the device node as no rewind See Creating No Rewind Device Nodes on page 16 for more information n the numeric character ide...

Page 15: ... number by one and so on for each successive tape device You can have up to 32 tape devices per mode Mode Auto Rewind Node example a a The 0 in this table is an example representing the device In actual practice this numeric character may be any num ber from 0 to 31 depending on the node No Rewind Node example Alpha Character Identification 1 st0 nst0 no character 2 st0l nst0l lowercase l 3 st0m n...

Page 16: ...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 Mode SCSI Tape Device Command 1 First mknod m 666 dev st0 c 9 0 1 Second mknod m 666 dev st1 c 9 1 2 First mknod m 666 dev st0l c 9 32 2 Second mknod m 666 dev st1l c 9 33 3 First mknod m 666 dev st0m c 9 64 3 Second mknod m 666 dev st1m c 9 65 4 First mknod m 66...

Page 17: ...talled To check whether mt st is installed execute the following command rpm qa grep mt st This command returns the name of the package followed by a version number for example RHEL3 returns mt st 0 7 11 If no information is returned mt st is not installed on your system To install mt st see Installing mt st Installing mt st 0 mt st is usually included on your Linux installation CD ROM To install ...

Page 18: ...re stinit def file is stored By default stinit searches your present working directory to find the stinit def file If stinit cannot find stinit def in the working directory it searches etc stinit def For more information on stinit see the stinit 8 man page Tape Device and Parameter Definitions 0 The stinit def file contains definitions of tape devices and their corresponding initialization paramet...

Page 19: ...s For a more thorough description of the keywords used for tape devices and parameters see the following references stinit 8 man page st 4 man page usr src linux kernel revision drivers scsi README st Appendix C Sample stinit def Definitions File on page 26 Note You may abbreviate some keywords Some keywords show a portion of the word enclosed within square brackets The portion enclosed within the...

Page 20: ...d rpm qa mtx This command returns the name of the package followed by a version number for example RHEL2 1 returns mtx 1 2 13 1 If no information is returned mtx is not installed on the system To install mtx see Installing mtx 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 ress...

Page 21: ... 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 ...

Page 22: ...ridge Compatibility DLT 0 Drive Type Tape Cartridge DLT 2000 DLT 2500 DLT 2700 DLT 2000XT DLT 2500XT DLT 2700XT DLT 4000 DLT 4500 DLT 4700 DLT 7000 DLT 8000 DLTtape III CompacTape III 10 20 GB 10 20 GB read only 10 20 GB read only 10 20 GB read only 10 20 GB read only DLTtape IIIXT CompacTape III XT N A 15 30 GB 15 30 GB read only 15 30 GB read only 15 30 GB read only DLTtape IV CompacTape IV N A ...

Page 23: ... 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 110 220 GB read only 160 320 GB read only Super DLTtape II N A N A 300 600 GB DLTtape VS1 N A N A 80 160 GB read only Cleaning Tape III N A N A N A SDLT Cleaning Tape 20 uses 20 uses 20 uses Drive Type Tape Cartridge DLT1 VS80 VS160 DLT V4 DLTtape IV CompacTape IV 40 80 GB 40 80 GB 40 80 ...

Page 24: ... and Cartridge Compatibility DDS DAT 0 Drive Type Tape Cartridge LTO 1 LTO 2 LTO 3 Ultrium 1 100 200 100 200 read only 100 200 read only Ultrium 2 N A 200 400 200 400 read only Ultrium 3 N A N A 400 800 Ultrium Cleaning Tape 20 uses 20 uses 20 uses Drive Type Tape Cartridge DDS3 DDS4 SP40 DAT 72 DDS2 4 8 4 8 N A DDS3 12 24 12 24 12 24 DDS4 N A 20 40 20 40 DAT 72 N A N A 36 72 Cleaning Tape 40 uses...

Page 25: ...nux 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 version stinit def examples st 4 man page dmesg 8 man page usr src linux kernel revision Documentation devices txt usr src linux kernel revision drivers scsi README st mt 1 man page mtx 1 man page ...

Page 26: ... modify this information as needed You may also create your own stinit def file Sample File 0 Red Hat Linux 9 0 EL 2 1 EL 3 0 Novell SuSE Linux 8 0 9 0 Quantum Corporation Jeff Willener 8 29 2003 Initial Release 12 20 2004 Add SDLT600 Support 6 17 2005 Add LTO LTO2 LTO3 support 11 1 2005 Add DAT72 DLT V4 support See also man page stinit 8 usr share doc mt st stinit def examples man page st 4 man p...

Page 27: ... off DLTtape VS1 0x99 160 0 GB compression on DLTtape VS1 BNCHMARK DLT1 0x40 40 0 GB DLTtape IV 0x86 40 0 GB compression off DLTtape IV 0x87 80 0 GB compression on DLTtape IV usr src linux kernel revision Documentation devices txt 9 Kernel Device Index Number char Character Device 0 255 SCSI Tape Device Node 9 char SCSI tape devices 0 dev st0 First SCSI tape mode 0 1 dev st1 Second SCSI tape mode ...

Page 28: ...eout long timeout 14400 4 hour long timeout can partitions 0 mode1 blocksize 0 density 0x49 compression 1 SDLT320 density compression on mode2 blocksize 0 density 0x49 compression 0 SDLT320 density compression off mode3 blocksize 0 density 0x48 compression 1 SDLT220 density compression on mode4 blocksize 0 density 0x48 compression 0 SDLT220 density compression off QUANTUM SDLT220 manufacturer QUAN...

Page 29: ...UM density compression off CERTANCE ULTRIUM manufacturer SEAGATE model ULTRIUM06242 XXX timeout 800 long timeout 14400 can partitions 0 mode1 blocksize 0 density 0x40 compression 1 ULTRIUM density compression on mode2 blocksize 0 density 0x40 compression 0 ULTRIUM density compression off mode3 blocksize 0 density 0x40 compression 1 ULTRIUM density compression on mode4 blocksize 0 density 0x40 comp...

Page 30: ...on 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 compression off BNCHMARK VS80 manufacturer BNCHMARK model DLT1 timeout 180 long timeout 14400 can partitions 0 mode1 blocksize 0 density 0x40 compression 1 VS80 density compression on mode2 blocksize 0 density 0x40 compression 0 VS80 ...

Page 31: ...verify mt st is installed mt st is not installed Install mt st see Installing mt st on page 17 No information is returned when you execute the command rpm qa mtx to verify mtx is installed mtx is not installed Install mtx see Installing mtx on page 21 modinfo st reports the st module name not found st module is not loaded Load the st module Consult your Linux manuals for instructions The st device...

Page 32: ...ions 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 You don t have enough st tape device nodes Verify that you have enough st tape device nodes for all your attached tape devices If you need to create more see instructions in the following sections Identifying Device Modes on page 15 Cre...

Reviews: