Toaddsupportfor anewIBM tapesubsystemtothesystemortoremovesupport for apreviouslyattachedIBM tapesubsystem,thefollowingstepsshouldbe performed:
1. EdittheIBMtape.conf fileinthe/usr/kernel/drvdirectorytoreflectthechangein IBMdevicesupport.Either adda newstanza toprovidesupportforadevice thatistobeadded,orremove(commentout)astanza foradevicethatisno longertobesupported.
2. Whenaddingsupportfora newdevice,ensurethatthetarget andLUNvalues intheconfigurationfilestanzamatchthetargetandLUNsettingsof theIBM device.See“ConfigurationParameters”onpage169 formoreinformation abouttheIBMtape.confconfigurationfile.
3. Shut downandpowerOff thehostsystem.
4. PlugthenewdeviceintotheSCSIbus,or unplugtheexistingdevicefromthe bus. Payparticularattention toproperSCSIcablingandtermination.
5. PowerOnand bootthehostsystem.
Note: Itispossibletoreinitialize theIBMtapedevicedriverwithoutrebooting thesystem.Thisisdonebyfirst unloadingthedevicedriver,then reloadingthedevicedriverintokernelmemory.
Thecommandtounloadthedevicedriveris:
% /usr/sbin/rem_drv IBMtape
Thecommandtoreloadthedevicedriveris:
% /usr/sbin/add_drv -m ’* 0666 bin bin’ IBMtape
WhentheIBMtapedevicedriverisreloaded,itreadstheIBMtape.conffile,and changes madeinthefileareacknowledged bythedevicedriver.Thismethod canbeusedtomodifyconfigurationparameters.
Solaris Device Driver (IBMtape)
Note: ItisstronglysuggestedthatyoupowerOffthehostsystemand all devicesattachedtotheSCSIbusbeforeadding orremovingdevicesfrom theSCSI bus.HotpluggingSCSIdevices cancausehardwaredamage anddisruptionofreliablesystemoperation.
Solaris Device Driver (IBMtape)
Chapter32.Installation,Removal,andConfiguration 173
Solaris Device Driver (IBMtape)
Chapter 33. Special Files
AftertheIBMtapedriverisinstalled,aset ofspecialfilesisavailablefor
performingI/Ooperationstoeachsupporteddevice.Thedevicespecial filenames created bytheIBMtapedevicedriveraresimilartotheSCSItapespecialfiles generallyusedonSolarissystems.
Eachtapeinstancehasaset ofminornumbersthatprovidesaccesstothesame physical device,buteachminor numberprovidesa differentfunctionorbehavior forthetapesubsystem.Theseminornumbersareaccessedthrough variationsof thespecial filenameforthatdevice.Thespecialfilesarecreated inthe/dev/rmt directory. Thesespecial filesareactuallysymboliclinkstofiles createdwithinthe /devices subdirectoryhierarchy.
Issuing thels-la/dev/rmtcommandpresentssomeusefulinformationaboutthese devicespecial files.Thefollowingisa representativeexampleoftheentries returnedbythiscommandfor asingleIBM tapesubsystem.Thislisting issystem dependent;thereforeentriesvariesslightlyinformat,dependingontheplatform and theSCSI adaptersupport.Theremayalsobe entriesincludedforotherdevices thatare notsupportedbytheIBMtapedevicedriver.
lrwxrwxrwx root other 79 Aug 26 18:54 0smc ->
/devices/iommu@f,e0000000/sbus@f,e0001000/QLGC,isp@3, 10000/IBMtape@2,0:smc
lrwxrwxrwx root other 78 Aug 26 18:54 0st ->
/devices/iommu@f,e0000000/sbus@f,e0001000/QLGC,isp@3, 10000/IBMtape@2,0:st
lrwxrwxrwx root other 79 Aug 26 18:54 0stb ->
/devices/iommu@f,e0000000/sbus@f,e0001000/QLGC,isp@3, 10000/IBMtape@2,0:stb
lrwxrwxrwx root other 80 Aug 26 18:54 0stbn ->
/devices/iommu@f,e0000000/sbus@f,e0001000/QLGC,isp@3, 10000/IBMtape@2,0:stbn
lrwxrwxrwx root other 79 Aug 26 18:54 0stc ->
/devices/iommu@f,e0000000/sbus@f,e0001000/QLGC,isp@3, 10000/IBMtape@2,0:stc
lrwxrwxrwx root other 80 Aug 26 18:54 0stcb ->
/devices/iommu@f,e0000000/sbus@f,e0001000/QLGC,isp@3, 10000/IBMtape@2,0:stcb
lrwxrwxrwx root other 81 Aug 26 18:54 0stcbn ->
/devices/iommu@f,e0000000/sbus@f,e0001000/QLGC,isp@3, 10000/IBMtape@2,0:stcbn
lrwxrwxrwx root other 80 Aug 26 18:54 0stcn ->
/devices/iommu@f,e0000000/sbus@f,e0001000/QLGC,isp@3, 10000/IBMtape@2,0:stcn
lrwxrwxrwx root other 79 Aug 26 18:54 0stn ->
/devices/iommu@f,e0000000/sbus@f,e0001000/QLGC,isp@3, 10000/IBMtape@2,0:stn
TheseentriesshowthedevicehierarchyestablishedtosupportI/OforanIBM SCSI tapesubsystem.Theattachmentpathofthedevicespecialfilesspansfrom thesystemboard, throughtheS-bus,totheSunF/WSCSIadapter(supportedby theQLGC,isp@SCSIadapterdevicedriver),totheIBM deviceatSCSItarget 2 and LUN0(supportedbytheIBMtapedevicedriver).All nineofthesespecialfiles are associatedwiththesameIBMdevice(devicenumber0).
Certain devicebehaviorsare determinedbywhichspecialfileinthesetisopened fordeviceaccess. Thesmcspecial filecontrolsonlythemediumchangerportionof
©CopyrightIBMCorp. 2000,2003 175
thedeviceandaccepts onlymediumchangeroperationsthrough theioctlentry point.Thesmcspecialfiledoesnotsupportthereadandwriteentrypoints.Only one sttype specialfileforaparticulardevicemaybe openedatanyonetime.The smcspecialfilemaybe openedconcurrentlywith anyoneofthestspecialfiles.
The IBMtapedevicedriverdecideswhichtypesofspecialfilestocreateduring installation,based ontheIBM devicetypebeingconfigured.FortheIBM3580-H11 Ultrium TapeDrive,onlytheeightstspecialfiles arecreated.FortheIBM3581 Ultrium TapeAutoloader,IBM 3583UltriumScalableTapeLibrary,and IBM3584 UltraScalableTape Library,allninespecial filesshownabovearecreated.
With theinformationfromthepreviouscommand,issuing thels-la
/devices/iommu@f,e0000000/sbus@f,e0001000/QLGC,isp@3,10000 commandpresents furtherinformationaboutthesamespecialfiles,asshowninthefollowing
example.Again,theactualpathinformationspecifiedinthecommandvariesfrom system tosystem.
crw-rw-rw- 1 bin bin 109,1696 Aug 26 18:54 IBMtape@2,0:smc crw-rw-rw- 1 bin bin 109,1664 Aug 26 18:56 IBMtape@2,0:st crw-rw-rw- 1 bin bin 109,1728 Aug 26 18:54 IBMtape@2,0:stb crw-rw-rw- 1 bin bin 109,1732 Aug 26 18:54 IBMtape@2,0:stbn crw-rw-rw- 1 bin bin 109,1688 Aug 26 18:54 IBMtape@2,0:stc crw-rw-rw- 1 bin bin 109,1752 Aug 26 18:54 IBMtape@2,0:stcb crw-rw-rw- 1 bin bin 109,1756 Aug 26 18:54 IBMtape@2,0:stcbn crw-rw-rw- 1 bin bin 109,1692 Aug 26 18:54 IBMtape@2,0:stcn crw-rw-rw- 1 bin bin 109,1668 Aug 26 18:54 IBMtape@2,0:stn
Theseentriesshowthemajorandminornumbersassociatedwith eachspecialfile.
Here, themajor numberis109andidentifies tothesystemthattheIBMtapedevice driverisinsupportof thesespecialfiles.Majornumbersareassignedbythe system atthetimethedriverisinstalledandvariesfromsystemtosystem.The ninedifferentminor numbersarespecific tothespecialfilenamesandareusedby thedevicedrivertodeterminewhichspecialfilewasusedtoaccessthedeviceand controlthedevicebehavioraccordingly.Forexample,theminornumber 1696 indicates toIBMtapethatthedevicewasopened throughthesmcspecialfile.For more informationondevicespecial filesandmajor/minornumbers,consultthe Solaris mtioman pages.
Table20showsthespecialfile-namingconventionandtheassociateddevice attributes recognizedbytheIBMtapedevicedriver.
Table20.IBMSCSITape/MediumChangerSpecialFilesforSolaris
SpecialFileName BSDCompatibility RewindonClose Compression
/dev/rmt/[0–255]smc N/A N/A N/A
Notes:
1. TheBSD(b)devicespecialfilemodifiesclosebehaviorfornon-rewinddevices.
Ifthedeviceisopened fornorewindon close,innon-BSDmode,if thelast commandbeforeclosingthedevicewasaread, thenthetapeispositionedafter thefilemarkimmediatelyfollowingthelastblockread.Ifthedeviceisopened forno rewindonclose,inBSDmode,ifthelastcommandbeforeclosingthe devicewasa read,thetapeisleftpositioned exactlywhereit wasfollowingthe lastblockread.Ifthedeviceisopened forrewindonclose,theBSDmodeis notrelevant.
2. Theno rewindonclose(n)devicespecial filedoesnotrewindthetapeduring a closeoperation.Otherwise,thetapeisrewound whenthedeviceisclosed.If thelastoperationbeforeclosingthedevicewasawriteorwritefilemark,then a sufficientnumberoffilemarksiswrittensothattwofilemarksfollowthe data.
For thenon-rewindspecial files,thetapesarepositioned betweenthetrailing filemarksbefore closing.Ifthedeviceisthenreopenedand moredatais written,itisseparatedbya singlefilemarkfromthepreviousdata.
3. Thecompression (c)devicespecialfiledetermineswhetherthetapedevice usesbuilt-inhardwarecompressionwhilestoringdataonthetape.The compressionmodeofthedevicecanalso besettothedesiredstate programmaticallythroughtheSTIOC_SET_PARMioctl,regardlessofthe defaultcompressionmodeestablishedbythespecialfileusedoriginallyto openthedevice.
4. ThesmcspecialfileiscreatedonlyforIBM tapesubsystemsthatprovide mediumchangercapability.For theIBM3580UltriumTape Drive,nosmc specialfileiscreated.
5. Onlyonestspecialfilemaybe openedatanyonetime.Thesmcspecialfile maybe openedbyitself orinconjunctionwith oneofthesttype files.Thesmc specialfileacceptsonlymediumchangercommands.Tapedrivecommands issuedto themediumchangerfailwith errnosetto22,invalidargument.
Asidefromthenormalconfigurationwiththemediumchangeranswering asa distincttarget andLUNpair, somesupporteddevicescanbe configuredwitha nonstandard integratedmediumchangerreportingatthesametargetand LUN asthetapedrive.Inthiscase,bothstandsmcspecialfiles accepta limited subsetofmediumchangercommands.Ifyouwanttousethisnonstandard mode, consulttheappropriatehardwarereference todeterminewhetherthe drivesupportssuchaconfiguration.
Solaris Device Driver (IBMtape)
Chapter33.SpecialFiles 177
Solaris Device Driver (IBMtape)
Chapter 34. Service and Diagnostic Aids
Thefollowingsection describestheserviceanddiagnosticaids thatarepartofthe IBMtapepackage.Itdiscussestheprocedureforverifyingthatthedevicedriver was installedcorrectly,provides basicproblemdetermination guidelines,and outlinestheutilityprogramincludedwiththeIBMtapepackage.