Administrator
|
This post was updated on .
(Transfered from old forum)
incorrect device type detected in TSM by nia » Wed Sep 01, 2010 3:41 pm Hi, I am using mhvtl-2010-08-11 https://sites.google.com/site/linuxvtl2/mhvtl-2010-08-11.tgz?attredirects=0&d=1 I have the following configured in MHVTL: Library: 140 CHANNEL: 16 TARGET: 00 LUN: 00 Vendor identification: STK Product identification: SL500 Product revision level: 1011 Unit serial number: 1401600 NAA: 140:22:33:44:ab:00:00:00 Drive: 141 CHANNEL: 16 TARGET: 01 LUN: 00 Library ID: 140 Slot: 01 Vendor identification: HP Product identification: Ultrium 3-SCSI Product revision level: G27D Unit serial number: 1411601 NAA: 140:22:33:44:ab:00:01:00 Compression: factor 1 enabled 1 READ_ONLY: LTO_1 READ_ONLY: LTO_2 READ_WRITE: LTO_3 WORM: LTO_3 # lsscsi -g [24:0:0:0] mediumx STK SL500 1011 /dev/sch1 /dev/sg8 [25:0:0:0] tape HP Ultrium 3-SCSI G27D /dev/st4 /dev/sg9 # mtx -f /dev/sg8 status Storage Changer /dev/sg8:4 Drives, 103 Slots ( 4 Import/Export ) Data Transfer Element 0:Empty Data Transfer Element 1:Empty Data Transfer Element 2:Empty Data Transfer Element 3:Empty Storage Element 1:Full :VolumeTag=HPT001L3 Storage Element 2:Full :VolumeTag=HPT002L3 Storage Element 3:Full :VolumeTag=HPT003L3 Storage Element 4:Full :VolumeTag=HPT004L3 Storage Element 5:Full :VolumeTag=HPT005L3 Using TSM 5.5.4.3: When running inventory for the library , TSM reports device of type STK "ECARTRIDGE" and not LTO ? tsm: TSM01>q libv SL500 Library Name Volume Name Status Owner Last Use Home Device Element Type ------------ ----------- ---------------- ---------- --------- ------- ------ SL500 HPT001L3 Scratch 1,024 ECART- RIDGE SL500 HPT002L3 Scratch 1,025 ECART- RIDGE SL500 HPT003L3 Scratch 1,026 ECART- RIDGE SL500 HPT004L3 Scratch 1,027 ECART- RIDGE SL500 HPT005L3 Scratch 1,028 ECART- RIDGE I am not sure what determines device type in MHVTL ? i.e LTO, DLT, ECARTRIDGE, 3590, 3592, 4MM, 8MM, OPTICAL and WORM Types, ..etc .. Is it the Library or drive type ?? ... Then I decided to change the library emulation from STK to ADIC to see if this makes a difference .. [66:0:0:0] mediumx ADIC Scalar i2000 100A /dev/sch1 /dev/sg8 [67:0:0:0] tape HP Ultrium 3-SCSI G27D /dev/st4 /dev/sg9 And yes, it does for TSM .. Now the device type is reported as "Blank" .. Still does not report device type "LTO" tsm: TSM01>q libv SL500 Library Name Volume Name Status Owner Last Use Home Device Element Type ------------ ----------- ---------------- ---------- --------- ------- ------ SL500 HPT001L3 Private DbBackup 1,024 SL500 HPT002L3 Private Data 1,025 SL500 HPT003L3 Scratch 1,026 SL500 HPT004L3 Scratch 1,027 SL500 HPT005L3 Scratch 1,028 Also writing to tape produces I/O error: 09/01/2010 18:00:00 ANR8302E I/O error on drive DRIVE1 (/dev/tsmscsi/mt4) with volume HPT002L3 (OP=WRITE, Error Number=0, CC=305, rc = 12, KEY=40, ASC=00, ASCQ=00, SENSE=F0.00.40.00.00.00.00.1E.00.00.00.00.00.00.00.00.00- .00.00.00.00.00. ------------------------------------------------------------------------------------------------- Re: incorrect device type in TSM by qssam80 » Thu Sep 02, 2010 2:33 pm I believe I have seen this before in mhvtl for TSM .. I think if you use an IBM library emulation then device type will show LTO And I think QUANTUM drives also do not show DLT for them as a device type in TSM as should. Only (STK drives + STK library) or (IBM drives + IBM library) emulation work fine in TSM. Others as HP, QUANTUM ..etc... do not match up device type correctly for TSM. Not sure what is going on !!! ... qssam80 ------------------------------------------------------------------------------------------------- Re: incorrect device type in TSM by nia » Thu Sep 02, 2010 10:14 pm Thanks, I should ping Mark Harvey for this .. ~nia ------------------------------------------------------------------------------------------------- Re: incorrect device type in TSM by qssam80 » Fri Sep 03, 2010 11:39 pm nia, I currently do not have access to mhvtl/TSM system, but perhaps you can run a TSM trace to see what shows up Just a thought ... ~Sam qssam80 ------------------------------------------------------------------------------------------------- Re: incorrect device type in TSM by nia » Sun Sep 05, 2010 4:40 am I have run some TSM traces already, but they do not tell anything wrong as TSM just picks up what ever the library tells .. [ExecuteAutoOp]:Issuing ioctl LIBRARY_INVENTORY (C0246C02) on library device /dev/tsmscsi/lb1. [85][mmsscsi.c][9352][RefreshSlotInfo]:Slot 0: addr=1024, useCode=FULL , devT=ANY, mediaT=-1, elemT=ANY. This was for SPECTRA /PYTHON Library and HP LTO-3 drive -- It shows Device Type listed as ANY instead of LTO .. [2:16:0:0] mediumx SPECTRA PYTHON 10.1 /dev/sch15 /dev/sg66 [2:16:1:0] tape HP Ultrium 3-SCSI R138 /dev/st46 /dev/sg50 tsm: TSM01>q libv sl500 Library Name Volume Name Status Owner Last Use Home Device Element Type ------------ ----------- ---------------- ---------- --------- ------- ------ SL500 ULT001L3 Private Data 1,024 SL500 ULT002L3 Scratch 1,025 ------------------------------------------------------------------------------------------------- Re: incorrect device type in TSM by nia » Thu Sep 23, 2010 2:14 pm I have repeated this test in TSM with mhvtl-2010-09-23.tgz / mhvtl-0.18-11 and following emulation: [33:0:0:0] mediumx STK L700 0315 /dev/sch1 /dev/sg9 [34:0:0:0] tape QUANTUM DLT-S4 1F1F /dev/st5 /dev/sg10 [35:0:0:0] tape QUANTUM DLT-S4 1F1F /dev/st6 /dev/sg11 Library content: # mtx -f /dev/sg9 status Storage Changer /dev/sg9:2 Drives, 208 Slots ( 9 Import/Export ) Data Transfer Element 0:Empty Data Transfer Element 1:Empty Storage Element 1:Full :VolumeTag=SDL001S4 Storage Element 2:Full :VolumeTag=SDL002S4 Storage Element 3:Full :VolumeTag=SDL003S4 Storage Element 4:Full :VolumeTag=SDL004S4 Storage Element 5:Full :VolumeTag=SDL005S4 And I still got the wrong device type for media in TSM, see below. TSM detecting device/media type of ECARTRIDGE instead of DLT, so it cannot write to it and complain about a mismatch. 09/23/2010 15:52:59 ANR9751E The volume in drive '/dev/tsmscsi/mt11' is not compatible with the drive. (SESSION: 26, PROCESS: 11) 09/23/2010 15:52:59 ANR8806E Could not write volume label SDL001S4 on the tape It seems like if the Library type, in this case STK L700, is forcing media/device type of ECARTRIDGE ? ------------------------------------------------------------------------------------------------- Re: incorrect device type in TSM by nia » Thu Sep 23, 2010 2:33 pm To add to the previous post: # dump_tape -f SDL001S4 PCL is : SDL001S4 Media density code: 0x4a Media type code : 0x33 Media description : SDLT II media Tape Capacity : 2097152000 Total num of filemarks: 0 Hdr: End of Data(05), sz 0, Blk No.: 0, data 0 SYSLOG at V3 shows: Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: fill_element_status_data_hdr: Starting slot: 1024, number of configured slots: 199 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: fill_element_status_data_hdr: Element Status Data HEADER: 04 00 00 c7 00 00 28 74 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: fill_element_status_data_hdr: Decoded: Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: fill_element_status_data_hdr: First element Address : 1024 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: fill_element_status_data_hdr: Number elements reported : 199 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: fill_element_status_data_hdr: Total byte count : 10356 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: resp_read_element_status: Returning 10364 bytes Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: decode_element_status: Element Status Data Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: decode_element_status: First element reported : 1024 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: decode_element_status: Number of elements available : 199 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: decode_element_status: Byte count of report : 10356 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: decode_element_status: Element Status Page Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: decode_element_status: Element Type code : 2 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: decode_element_status: Primary Vol Tag : Yes Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: decode_element_status: Alt Vol Tag : No Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: decode_element_status: Element descriptor length : 52 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: decode_element_status: Byte count of descriptor data: 10348 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: decode_element_status: Element Descriptor(s) : Num of Elements 199 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: dump_element_desc: Debug.... i = 0, len = 52 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: dump_element_desc: Element Address : 1024 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: dump_element_desc: Status : 0x09 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: dump_element_desc: Medium type : 1 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: dump_element_desc: Source Address : 47088 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: dump_element_desc: Voltag info... Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: dump_element_desc: Identification Descriptor Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: dump_element_desc: Code Set : 0x00 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: dump_element_desc: Identifier type : 0x00 Sep 23 14:25:47 scst-mhvtl vtllibrary[6359]: dump_element_desc: Identifier length : 0 messages.wrong.dev.type.zip ------------------------------------------------------------------------------------------------- Re: incorrect device type in TSM by markh794 » Thu Sep 23, 2010 4:32 pm OK, what what is TSM looking for ? There are no errors in the 'messages.wrong.dev.type.txt' How does TSM determine the 'device type' ? Cheers markh794 MHVTL - Developer ------------------------------------------------------------------------------------------------- Re: incorrect device type in TSM by nia » Thu Sep 23, 2010 4:53 pm OK, what is TSM looking for ? TSM needs to know that this media/device type is detected as "DLT" so it knows it can be nounted in the Drive defined DLT-S4.. Instead it sees ECART type which 1/2 inch used by STK drives and will not fit into a DLT drive. My question is where did the ECART media type come from ? I did not tell TSM to look for that. How does TSM determine the 'device type' ? I suspect, it runs an IOCTL to the library and based on what the Library tells, it sees. Here is a list of device/media type TSM uses for Tape: * 3590 * 3592 * 4MM * 8MM * DLT * ECARTRIDGE * LTO * OPTICAL * WORM * QIC * VOLSAFE ------------------------------------------------------------------------------------------------- Re: incorrect device type detected in TSM by markh794 » Fri Sep 24, 2010 1:58 am As far as the vtl is concerned, all we see is SCSI OP codes. It's up the the application software to interpret the returned information. What I need to know is: what information is TSM looking for to make the device/media type decision. Any ioctl() calls will eventually result in a SCSI OP code being sent thru to the library or drive.. In summary, my question is the same as yours: "My question is where did the ECART media type come from ? " Once we understand the answer, the appropriate SCSI OP code can be tuned / corrected to suit TSM's expectations. FWIW: NetBackup doesn't care. You as the NetBackup administrator define drives as type "hcart, hcart2, hcart3, dlt, dlt2, dlt3, 8mm, 8mm2 etc.. (there are lots of them)" Based on barcode rules, you set the media type to match the above drive type. NetBackup will then only allow "like" media to be placed in the same type drive (i.e. dlt2 media into a drive defined as dlt2).. In reality, the 'dlt2' defined drive could be a 4MM DAT drive.. NetBackup just cares that the drive & media type match. I would like to find the answer to TSM's behaviour. Does anybody have a support contract with TSM support where they could ask the question ? Cheers markh794 MHVTL - Developer ------------------------------------------------------------------------------------------------- Re: incorrect device type detected in TSM by nia » Sun Sep 26, 2010 2:28 pm I have run many TSM tracing to see what TSM does when tries to detect device/media type in the library but nothing can shed any light. I run a different test also where I changed my Library and Tape emulation to the following: [2:17:0:0] mediumx IBM 03584L32 4.02 /dev/sch16 /dev/sg72 [2:17:1:0] tape IBM ULT3580-TD3 6430 /dev/st47 /dev/sg51 [2:17:2:0] tape IBM ULT3580-TD3 6430 /dev/st48 /dev/sg52 [2:17:3:0] tape IBM ULT3580-TD3 6430 /dev/st49 /dev/sg53 [2:17:4:0] tape IBM ULT3580-TD3 6430 /dev/st50 /dev/sg54 [2:17:5:0] tape IBM ULT3580-TD3 6430 /dev/st51 /dev/sg55 Using IBM Lin Tape Driver: lin_tape-1.34.0-1.i386 MHVTL release 0.18-11 (9/23/2010) TSM 5.5.4.3 32-bit And then TSM was able to detect LTO type media fine with no issues .. Read/write is successful also. Library Name Volume Name Status Owner Last Use Home Device Element Type ------------ ----------- ---------------- ---------- --------- ------- ------ 03584L32 IBM001L3 Private Data 1,024 LTO 03584L32 IBM002L3 Private Data 1,025 LTO 03584L32 IBM003L3 Private Data 1,026 LTO 03584L32 IBM004L3 Private Data 1,027 LTO 03584L32 IBM005L3 Private Data 1,028 LTO 03584L32 IBM006L3 Scratch 1,029 LTO So in summary, there are only two type of library and drive emulation TSM can use with mhvtl as of right now: IBM Library/Drive type of LTO STK Library/Drive type of ECART Any other will not detect the correct device/media type in TSM library inventory and even cause core dump in TSM with any none ECART type drives used. i.e QUANTUM and HP LTO |
Administrator
|
"So in summary, there are only two type of library and drive emulation TSM can use with mhvtl as of right now:
IBM Library/Drive type of LTO STK Library/Drive type of ECART " Which point's to TSM. There is NO code difference between the two library 'emulation' except the ASCII data within the SCSI Inquiry strings. Unlike the tape side of things, there is no 'emulation' mode within the library code. It will respond the same no matter what is placed in device.conf. To "fix" this issue (well make the mhvtl more compatible with TSM), I need some sort of documentation on how TSM determines drive types. This way, I could include modified vltlibrary behaviour based on library type.. However until I know what is needed by TSM, I do not know what to modify. Can somebody/anybody supply this information - As I known nothing about TSM. Cheers Mark
Regards from Australia
Mark Harvey |
Free forum by Nabble | Edit this page |