background image

HP-UX Systems

16

To create device files using 

mksf

:

NOTE:

This method is 

not

 recommended.

1.

Run 

insf

 as follows:

% /sbin/insf -C tape

2.

Create the device files for the devices using the 

mksf

 command as follows:

% /sbin/mksf -d stape -I <instance> [-n] [-u] /dev/rmt/X<name>

where:

See the man page (

man 1m mksf

) for other options of the 

mksf

 command. The 

stape

 section 

covers the SCSI tape driver options. The man page 

man 7 mt

 describes the long filenames used 

in HP-UX 10.

x

 and later.

Example:

To create a device file with the following characteristics:

Argument

Description

-d stape

Specifies the SCSI tape driver

-I <instance>

Specifies the tape drive’s hardware address via the instance of the SCSI tape 

driver. The first instance is 0, the second 1, and so on.

[-n]

Specifies no rewind; absence of this parameter indicates rewind mode

[-u]

Specifies Berkeley mode; absence of this parameter indicates AT&T mode. 

Berkeley and AT&T modes differ in their read-only close behavior:

In Berkeley mode, the tape position will remain unchanged by a device 

close operation.

In AT&T mode, a device close operation will cause the tape to be 

repositioned just after the next tape filemark (the start of the next file).

In most cases, Berkeley mode should be used.

/dev/rmt/X<name>

Specifies the path of the device file, where:

X

Specifies the tape device identifier. Use the next available 

identifier. You can examine the contents of 

/dev/rmt

 using the 

ls

 command to determine which identifiers have already been 

used.

<name>

Specifies the short name (in HP-UX 9.x-style) of the device file:

mnb

No rewind, compression disabled, Berkeley-mode device

hnb

No rewind, compression disabled, Berkeley-mode device

mnb

No rewind, compression disabled, Berkeley-mode device

hnb

No rewind, compression enabled, Berkeley-mode device

Summary of Contents for Ultrium Drive

Page 1: ...HP Ultrium tape drives Technical reference manual Generation 3 drives Volume 5 Unix configuration guide Part number Q1538 90925 Volume 5 Edition 6 1 December 2004 ...

Page 2: ...pecial incidental or consequential damages in connection with the furnishing performance or use of this document This document contains proprietary information which is protected by copyright All rights reserved No part of this document may be photocopied reproduced or translated to another language without the prior written consent of Hewlett Packard Revision history This document is frequently r...

Page 3: ...HP Servers and Workstations HP UX 11 x 13 Introduction 13 Determining the SCSI ID 13 Creating the Device Files 14 What Next 17 3 HP Alpha UNIX HP Alpha UNIX 5 x 19 What Next 20 4 IBM AIX Determining the SCSI ID 21 Configuring the Device Files 21 5 Linux Determining the SCSI ID Linux 23 Configuring on Linux Systems 23 Using the Seek and Tell Features of mt 25 What Next 25 6 Sun Systems Solaris 8 9 ...

Page 4: ...4 Contents 7 Verifying the Installation Verifying the Installation of the Drive UNIX 31 To verify the installation 31 Example 32 Glossary 35 Index 39 ...

Page 5: ...g details are given below Related documents The following documents provide additional information Documents specific to HP Ultrium drives Hardware Integration Guide volume 1 of the HP Ultrium Technical Reference Manual Software Integration Guide volume 2 of the HP Ultrium Technical Reference Manual The SCSI Interface volume 3 of the HP Ultrium Technical Reference Manual Specifications volume 4 of...

Page 6: ...SI only 1 HW Integration ch 5 n a In Libraries 1 HW Integration ch 1 In Servers SCSI only 1 HW Integration ch 4 n a In Tape Arrays SCSI only 1 HW Integration ch 3 n a Modes of Usage SCSI only 1 HW Integration ch 8 n a Optimizing performance SCSI only 1 HW Integration ch 8 n a 2 SW Integration ch 4 UNIX configuration 5 UNIX Config SCSI Drives FC Drives External drives SCSI only 1 HW Integration ch ...

Page 7: ...ages see the MODE SENSE command 3 SCSI ch 4 Pre execution checks 3 SCSI ch 3 Responding to Sense Keys and ASC Q 2 SW Integration ch 6 Sense Keys and ASC Q see REQUEST SENSE command 3 SCSI ch 4 SCSI Drives FC Drives Cleaning 2 SW Integration ch 5 2 SW Integration ch 7 External drives SCSI only 1 HW Integration ch 5 n a In Libraries 1 HW Integration ch 1 In Servers SCSI only 1 HW Integration ch 4 n ...

Page 8: ...tegration ch 3 TapeAlert log 2 SW Integration ch 7 SCSI Drives FC Drives SCSI Drives FC Drives Adaptive Tape Speed ATS 6 Background ch 1 Autoload 1 HW Integration ch 2 Automation Control Interface ACI 1 HW Integration ch 2 6 Background ch 1 Cartridge Memory LTO CM 1 HW Integration ch 2 2 SW Integration ch 5 6 HW Integration ch 5 Data Compression how it works 6 Background ch 5 Data Compression mana...

Page 9: ...I 11 West 42nd Street New York NY 10036 8002 USA ISO CP 56 CH 1211 Geneva 20 Switzerland ECMA 114 Rue du Rhône CH 1204 Geneva Switzerland Tel 41 22 849 6000 Web URL http www ecma ch Global Engineering Documents 2805 McGaw Irvine CA 92714 USA Tel 800 854 7179 or 714 261 1455 ...

Page 10: ...10 ...

Page 11: ...onnectivity details available that arrived after the release notes were published See Chapter 7 for details of how to verify the installation Ultrium Drives in a Library Ultrium drives may also be used in a library However instructions about installing device drivers for automatic robotics are not included in this manual Backup Applications For optimum performance it is important to use a backup a...

Page 12: ...full use of the drive s functions please contact the software manufacturer or HP 1 Cell Manager is only available on HP UX or Windows 2 Redhat Server only not Caldera Suse and so on HP UX AIX Sun Solaris Linux HP Omniback1 yes yes yes yes Legato Networker yes yes yes yes Veritas NetBackup yes yes yes yes2 ...

Page 13: ...ate H W Type Description bc 0 root CLAIMED BUS_NEXUS bc 1 8 bc CLAIMED BUS_NEXUS Psudo Bus Converter ba 0 8 0 GSCtoPCI CLAIMED BUS_NEXUS GSCtoPCI Bridge ext_bus 1 8 0 2 0 c720 CLAIMED INTERFACE SCSI C895 Ultra2 Wide LVD target 0 8 0 2 0 7 tgt CLAIMED DEVICE ctl 1 8 0 2 0 7 0 sctl CLAIMED DEVICE Initiator lan 0 8 0 20 0 btlan3 CLAIMED INTERFACE PCI 10110019 Built in 1 ba 1 8 16 bus_adapter CLAIMED ...

Page 14: ...ighlight the stape driver If the driver has not been added to the kernel both Current State and Pending State will read Out 4 Select the following Actions Add Driver to Kernel The Pending State will now read In 5 To add the new driver to the kernel select Actions Create a New Kernel 6 The stape driver will now be added to the kernel and then the system will reboot Creating the Device Files Once yo...

Page 15: ...vice files for the drive To view the device files that have been created select Actions Create Device Files Show Device Files where 4 When you have exited sam run ioscan to see the tape drive sbin ioscan C tape fn Device File Description I is the instance number of the drive I m I mn I mb I mnb AT T encoding rewind driver AT T encoding non rewind driver Berkeley encoding rewind driver Berkeley enc...

Page 16: ...ameter indicates rewind mode u Specifies Berkeley mode absence of this parameter indicates AT T mode Berkeley and AT T modes differ in their read only close behavior In Berkeley mode the tape position will remain unchanged by a device close operation In AT T mode a device close operation will cause the tape to be repositioned just after the next tape filemark the start of the next file In most cas...

Page 17: ...ng output to show that the device file now exists stape card instance 0 SCSI target 6 SCSI LUN 0 berkeley no rewind BEST density at address 2 0 1 6 0 dev rmt 4mnb To create a device file for Ultrium in uncompressed mode you should use a command such as mksf H a b U_18 and for compressed mode default mksf H a b U_18C The hardware path can be found from previous ioscan output What Next Once the devi...

Page 18: ...HP UX Systems 18 ...

Page 19: ...kSize 262144 TagQueueDepth 0 MaxTransferSize 0xffffff 16Mb 1 ReadyTimeSeconds 120 Seconds SyncTransfers enabled WideTransfers enabled InquiryLength 0x20 DENSITY DensityNumber 0 1 2 3 4 5 6 7 OneFileMarkOnClose yes DensityCode 0x44 Blocking 0 CompressionCode 1 Buffered 1 Speed 0 MODESELECT ModeSelectNumber 0 SavePage No PageFormat scsi2 BlockDescriptor yes TransferLength 16 Hdr Tape BufferMode 0x1 ...

Page 20: ...es in the dev ntape directory are no rewind devices Those in dev tape will do a rewind on close The device files then have the syntax tapeX_dn For example dev ntape tape66_d1 is a device file for device 66 no rewind using density number 1 Since all density numbers have the same parameters it does not matter which density number file is used What Next Once the device files have been created you sho...

Page 21: ...iguring the Device Files To install an HP Ultrium drive on an IBM workstation you will need to create the appropriate device files for the drive NOTE Do not choose the smit option of 4mm2gb as the Tape Device Type This is reserved for Connor drives If you use it with HP drives you will get the error Device to be configured does not match the physical device at the specified connection location To ...

Page 22: ...d below for the combination of Rewind on Close Retension on Open and Compression that you want The n in the filename is the instance number assigned to the drive by the operating system where 0 is the first device 1 is the second and so on Filename Rewind on Close Retension on Open Compression dev rmtn Yes No enabled dev rmtn 1 No No enabled dev rmtn 2 Yes Yes enabled dev rmtn 3 No Yes enabled dev...

Page 23: ...NSI SCSI Revision 02 Look at the ID information to establish which IDs are in use Configuring on Linux Systems No changes are needed to support Ultrium on Linux platforms however you should ensure that you have the relevant drivers loaded To see the device drivers loaded currently execute an lsmod command this will give output like Module Size Used by sgm 4376 1 ide scsi 7200 0 lockd 30792 1 sunrp...

Page 24: ...e dmesg grep st This should find a number of lines One should look like Detected SCSI tape st0 at scsi1 channel 0 id 5 lun 0 To load the tape driver module if it is not loaded as above execute insmod st to load it This should happen naturally if your system is rebooted after attaching the drive When the ST driver module has been added a list of tape device files will be created automatically They ...

Page 25: ...essing You can do this by using the command mt f device file stsetoptions scsi2logical where dev stp is the device file Note however that this information is not preserved across reboots so you need to execute this command each time the system comes up The stinit utility offers a convenient way of handling this see the relevant man page for more information If you use this approach set the manufac...

Page 26: ...Linux 26 ...

Page 27: ...1272c 228 1 qus isp10160 HBA Driver For the adapter to which the new tape drive is attached you will need to determine what SCSI IDs are already used 2 Determine the SCSI IDs of the existing devices attached to the SCSI controller For all adapters dmesg egrep xxx target sort uniq where xxx the type of adapter esp glm fas qus or isp as appropriate For example for an ESP based adapter dmesg egrep es...

Page 28: ...c 1992 by Sun Microsystems Inc ident st conf 1 6 93 05 03 SMI add the following depending on which version of operating system you are installing there are 6 significant spaces between HP and Ultrium in line 2 for Solaris 8 without st patch tape config list HP Ultrium 3 HP Ultrium LTO 3 HP_LTO_GEN_3 HP_LTO_GEN_3 1 0x36 0 0xd639 4 0x44 0x44 0x44 0x44 3 name st class scsi target X lun 0 where X is t...

Page 29: ... that your new tape drive is working properly Chapter 7 Verifying the Installation provides instructions on backing up and restoring a sample file to test your installation HP Data Values The values for HP_LTO_GEN_n and name which provide normal LTO mode have the following meanings The syntax for HP_LTO_GEN_n on Solaris 9 is drive type version type bsize options no of densities density 0 density 1...

Page 30: ...nloadable 0x1000 Time outs five times longer than normal 0x4000 Driver buffers write requests and pre acknowledges success to application 0x8000 Variable record size not limited to 64 KB 0x10000 Device determines which of the two mode pages the device supports for selecting or deselecting compression So 0xd639 indicates variable record length bsf and bsr enabled long timeouts for erase EOD recogni...

Page 31: ...ead from the tape with the original data on disk To verify the installation 1 Test the SCSI connection to the tape drive by doing a rewind operation a If there is a tape cartridge already in the drive remove it b Insert a tape cartridge c Rewind the tape using the command line mt f device file rewind For example on HP UX mt f dev rmt 0mnb rewind If the command completes successfully there will be ...

Page 32: ... tmp retrieved file This step compares the retrieved file and the original file byte by byte If they are the same there should be no output and this verifies that the installation is correct The arguments are as follows Example Suppose you are verifying the installation of an HP Ultrium tape drive on an HP UX 11 X system The procedure would be as follows 1 Change directory to root cd 2 Back up sta...

Page 33: ...ng the Installation 33 3 Change to the temporary directory cd tmp 4 Extract the file from the tape tar xvf dev rmt 0m 5 Compare the original with the restored version cmp stand vmunix tmp stand vmunix Note that the original filename is not prefixed with ...

Page 34: ...Verifying the Installation 34 ...

Page 35: ... drives the data is compressed using the LTO DC compression format which is based on ALDC licensed from Stac IBM with two enhancements One limits the increase in size of data that cannot be compressed that ALDC produces The other is the use of embedded codewords data transfer phase On a SCSI bus devices put in requests to be able to transfer information Once a device is granted its request it and ...

Page 36: ...performance of systems that do not set the Immediate bit when sending a SCSI WRITE FILEMARKS command On the other hand data is not flushed to tape in response to a filemark command infinite flush By default the buffer in the drive is flushed every 5 seconds Infinite flush avoids frequent starting and stopping of the mechanism when using a very slow application It also avoids losing capacity throug...

Page 37: ...r two bytes of data simultaneously 16 bit SCSI They usually have a single 68 pin connection to the SCSI bus This physical arrangement is part of the SCSI 3 specification They may support either SCSI 2 or SCSI 3 protocols Wide and narrow devices can simultaneously be connected to the same bus without problem provided certain rules are followed Fast SCSI can transfer data at up to 10 MB sec using a ...

Page 38: ... the order in which it is received Tape devices are the most common sequential access devices Devices such as disk drives are direct access devices where data is stored in blocks not necessarily sequentially Direct access allows for speed of retrieval but is significantly more costly ...

Page 39: ...device files 14 I IBM AIX 21 determining SCSI ID 21 device files 21 immediate mode 36 infinite flush 36 installation verifying 31 L Linux 23 determining SCSI ID 23 LUN 36 LVD SCSI 37 M mode AT T 35 Berkeley 35 immediate 36 N narrow SCSI 37 P PC based UNIX Linux 23 S SCSI 5 36 SCSI ID determining HP UX 13 IBM AIX 21 Linux 23 Sun workstations 27 sequential access 38 single ended SCSI 37 Sun workstat...

Page 40: ...Index 40 ...

Reviews: