Having an issue with serial numbers being returned correctly running mhVTL 1.4-8 and stgt 1.0.17 (This also happens on 1.4-10 and 1.0.41). What am I missing here?! I looks like there's some additional characters in the SERIAL return data that do not appear in the device.conf file.
11/5/2013 15:19:55.528 Execute "Inquiry (12h)" command, EVPD 1, page code 0x80 (128), allocation length 11/5/2013 15:19:55.528 0x00FF (255), CDB length 6, CDB (hex) 12 01 80 00 FF 00 11/5/2013 15:19:55.653 Dump data size 0x0000001A (26) byte(s), dump data (hex): 11/5/2013 15:19:55.653 00000000: 08 80 00 16 08 80 00 10 37 30 30 30 30 30 37 30 .€...€..70000070 11/5/2013 15:19:55.653 00000010: 20 00 00 00 31 30 32 00 00 00 ...102... 11/5/2013 15:19:55.653 Received 26 bytes of inqury data 11/5/2013 15:19:55.668 Peripheral qualifier 0, peripheral device type 0x08 (8), page code 0x80 (128), p 11/5/2013 15:19:55.668 age length 22 11/5/2013 15:19:55.668 Unit Serial Number (80h) page 11/5/2013 15:19:55.668 Unit serial number: € 11/5/2013 15:19:55.715 "Inquiry (12h)" command completed, adapter status 0 <Success>, SCSI status: 0x00 11/5/2013 15:19:55.715 <Good>, execution time 127209 mcs [root@vtl ~]# cat /etc/mhvtl/device.conf VERSION: 5 # VPD page format: # <page #> <Length> <x> <x+1>... <x+n> # NAA format is an 8 hex byte value seperated by ':' # Note: NAA is part of inquiry VPD 0x83 # # Each 'record' is separated by one (or more) blank lines. # Each 'record' starts at column 1 # Serial num max len is 10. # Compression: factor X enabled 0|1 # Where X is zlib compression factor 1 = Fastest compression # 9 = Best compression # enabled 0 == off, 1 == on # # fifo: /var/tmp/mhvtl # If enabled, data must be read from fifo, otherwise daemon will block # trying to write. # e.g. cat /var/tmp/mhvtl (in another terminal) Library: 50 CHANNEL: 1 TARGET: 00 LUN: 00 Vendor identification: IBM Product identification: 03584L22 Product revision level: 4.02 Unit serial number: 70000050 NAA: 50:11:22:33:ab:1:00:00 Home directory: /opt/mhvtl/50 Backoff: 400 Drive: 51 CHANNEL: 1 TARGET: 00 LUN: 01 Library ID: 50 Slot: 01 Vendor identification: IBM Product identification: ULTRIUM-TD5 Product revision level: 252D Unit serial number: 70000051 NAA: 50:11:22:33:ab:1:00:01 Compression: factor 1 enabled 1 Compression type: lzo Backoff: 400 Drive: 52 CHANNEL: 1 TARGET: 00 LUN: 2 Library ID: 50 Slot: 2 Vendor identification: IBM Product identification: ULTRIUM-TD5 Product revision level: 252D Unit serial number: 70000052 NAA: 50:11:22:33:ab:1:00:2 Compression: factor 1 enabled 1 Compression type: lzo Backoff: 400 Drive: 53 CHANNEL: 1 TARGET: 00 LUN: 3 Library ID: 50 Slot: 3 Vendor identification: IBM Product identification: ULTRIUM-TD5 Product revision level: 252D Unit serial number: 70000053 NAA: 50:11:22:33:ab:1:00:3 Compression: factor 1 enabled 1 Compression type: lzo Backoff: 400 Drive: 54 CHANNEL: 1 TARGET: 00 LUN: 4 Library ID: 50 Slot: 4 Vendor identification: IBM Product identification: ULTRIUM-TD5 Product revision level: 252D Unit serial number: 70000054 NAA: 50:11:22:33:ab:1:00:4 Compression: factor 1 enabled 1 Compression type: lzo Backoff: 400 Library: 70 CHANNEL: 2 TARGET: 00 LUN: 00 Vendor identification: IBM Product identification: 03584L32 Product revision level: 4.02 Unit serial number: 70000070 NAA: 70:11:22:33:ab:2:00:00 Home directory: /opt/mhvtl/70 Backoff: 400 Drive: 71 CHANNEL: 2 TARGET: 00 LUN: 01 Library ID: 70 Slot: 01 Vendor identification: IBM Product identification: ULTRIUM-TD6 Product revision level: 252D Unit serial number: 70000071 NAA: 70:11:22:33:ab:2:00:01 Compression: factor 1 enabled 1 Compression type: lzo Backoff: 400 Drive: 72 CHANNEL: 2 TARGET: 00 LUN: 2 Library ID: 70 Slot: 2 Vendor identification: IBM Product identification: ULTRIUM-TD6 Product revision level: 252D Unit serial number: 70000072 NAA: 70:11:22:33:ab:2:00:2 Compression: factor 1 enabled 1 Compression type: lzo Backoff: 400 Drive: 73 CHANNEL: 2 TARGET: 00 LUN: 3 Library ID: 70 Slot: 3 Vendor identification: IBM Product identification: ULTRIUM-TD6 Product revision level: 252D Unit serial number: 70000073 NAA: 70:11:22:33:ab:2:00:3 Compression: factor 1 enabled 1 Compression type: lzo Backoff: 400 Drive: 74 CHANNEL: 2 TARGET: 00 LUN: 4 Library ID: 70 Slot: 4 Vendor identification: IBM Product identification: ULTRIUM-TD6 Product revision level: 252D Unit serial number: 70000074 NAA: 70:11:22:33:ab:2:00:4 Compression: factor 1 enabled 1 Compression type: lzo Backoff: 400 [root@vtl ~]# |
Administrator
|
Any chance of testing from the mhVTL side of things ?
e.g. # lsscsi -g (identify one of the mhVTL devices via the '/dev/sg' path Then run the 'sg_inq' from the sg3_utils package: # sg_inq -H -p 0x80 /dev/sg9 e.g. # sg_inq -H -p 0x80 /dev/sg9 VPD INQUIRY, page code=0x80: 00 01 80 00 0a 58 59 5a 5a 59 5f 41 31 35 20 ....XYZZY_A15 Note that only 16 bytes are returned not the 26 bytes your log is indicating.. Trying the library device & the 'sg_raw' command as an alternate test: # sg_raw -r 1k /dev/sg10 12 01 80 00 FF 00 SCSI Status: Good Sense Information: sense buffer empty Received 18 bytes of data: 00 08 80 00 0e 41 30 43 30 30 34 35 34 32 31 5f 4c ....A0C0045421_L 10 4c 42 LB
Regards from Australia
Mark Harvey |
Hi MArk,
here is my CA Arcserve log: [11/13 12:54:08 0574 1 DM 5] TapeDrive [2] ABSL:3061 <ULT3580-TD5 A3K6> S/N[10000111 ] [11/13 12:54:08 0574 1 DM 5] TapeDrive [3] ABSL:3062 <ULT3580-TD5 A3K6> S/N[10000112 ] [11/13 12:54:08 0574 1 DM 5] Library [4] ABSL:3063 <ULT3582-TL 205B> S/N[ €] [11/13 12:54:08 0574 1 DM 5] TapeDrive [6] ABSL:3001 <ULT3580-TD5 A3K6> S/N[10000061 ] [11/13 12:54:08 0574 1 DM 5] Library [7] ABSL:3002 <ULT3582-TL 205B> S/N[ €] [11/13 12:54:08 0574 1 DM 5] Library [9] ABSL:3011 <ULT3582-TL 205B> S/N[ €] [11/13 12:54:08 0574 1 DM 5] TapeDrive [10] ABSL:3012 <ULT3580-TD5 A3K6> S/N[10000011 ] [11/13 12:54:08 0574 1 DM 5] TapeDrive [11] ABSL:3013 <ULT3580-TD5 A3K6> S/N[10000012 ] [11/13 12:54:08 0574 1 DM 5] TapeDrive [12] ABSL:3014 <ULT3580-TD5 A3K6> S/N[10000013 ] [11/13 12:54:08 0574 1 DM 5] TapeDrive [14] ABSL:3021 <ULT3580-TD5 A3K6> S/N[10000032 ] [11/13 12:54:08 0574 1 DM 5] TapeDrive [15] ABSL:3022 <ULT3580-TD5 A3K6> S/N[10000033 ] [11/13 12:54:08 0574 1 DM 5] TapeDrive [16] ABSL:3023 <ULT3580-TD5 A3K6> S/N[10000034 ] [11/13 12:54:08 0574 1 DM 5] Library [17] ABSL:3024 <ULT3582-TL 205B> S/N[ €] [11/13 12:54:08 0574 1 DM 5] TapeDrive [18] ABSL:3025 <ULT3580-TD5 A3K6> S/N[10000031 ] [11/13 12:54:08 0574 1 DM 5] TapeDrive [20] ABSL:3031 <ULT3580-TD5 A3K6> S/N[10000091 ] [11/13 12:54:08 0574 1 DM 5] Library [21] ABSL:3032 <ULT3582-TL 205B> S/N[ €] [11/13 12:54:08 0574 1 DM 5] TapeDrive [23] ABSL:3041 <ULT3580-TD5 A3K6> S/N[10000021 ] [11/13 12:54:08 0574 1 DM 5] Library [24] ABSL:3042 <ULT3582-TL 205B> S/N[ €] [11/13 12:54:08 0574 1 DM 5] TapeDrive [26] ABSL:3051 <ULT3580-TD5 A3K6> S/N[10000041 ] [11/13 12:54:08 0574 1 DM 5] TapeDrive [27] ABSL:3052 <ULT3580-TD5 A3K6> S/N[10000042 ] [11/13 12:54:08 0574 1 DM 5] Library [28] ABSL:3053 <ULT3582-TL 205B> S/N[ €] As you can see, some problems on library serial numbers. Here is 1 of these on ubuntu server: sudo lsscsi -g [1:0:0:0] cd/dvd NECVMWar VMware IDE CDR10 1.00 /dev/sr0 /dev/sg0 [2:0:0:0] disk VMware Virtual disk 1.0 /dev/sda /dev/sg1 [2:0:1:0] disk VMware Virtual disk 1.0 /dev/sdb /dev/sg2 [4:9:0:0] mediumx IBM ULT3582-TL 205B /dev/sch0 /dev/sg5 [4:9:0:1] tape IBM ULT3580-TD5 A3K6 /dev/st0 /dev/sg3 [4:9:0:2] tape IBM ULT3580-TD5 A3K6 /dev/st1 /dev/sg4 sudo sg_inq -H -p 0x80 /dev/sg5 VPD INQUIRY, page code=0x80: 00 08 80 00 16 08 80 00 10 31 30 30 30 30 31 31 30 ........10000110 10 20 00 00 00 31 30 32 00 00 00 ...102... sudo sg_inq -H -p 0x80 /dev/sg3 VPD INQUIRY, page code=0x80: 00 01 80 00 0a 31 30 30 30 30 31 31 31 20 20 ....10000111 sudo sg_inq -H -p 0x80 /dev/sg4 VPD INQUIRY, page code=0x80: 00 01 80 00 0a 31 30 30 30 30 31 31 32 20 20 ....10000112 sudo sg_raw -r 1k /dev/sg5 12 01 80 00 FF 00 SCSI Status: Good Sense Information: sense buffer empty Received 26 bytes of data: 00 08 80 00 16 08 80 00 10 31 30 30 30 30 31 31 30 ........10000110 10 20 00 00 00 31 30 32 00 00 00 ...102... I hope this can help. Regards |
Administrator
|
In reply to this post by cv
wow - I apologise..
I just didn't "understand" what you were trying to say here.. Hindsight is a wonderful thing. This patch should fix the error. 0001-Correct-VPD-updates-for-library-personality-modules.patch It will apply cleanly to 1.5-0 rpm source / 2014-03-13 tar ball / git head..
Regards from Australia
Mark Harvey |
Hello,
the patch works ok, the vpd serial issue is resolved now. thanks! ally |
In reply to this post by Mark Harvey
how can fix this problem
download 0001-Correct-VPD-updates-for-library-personality-modules.patch put it to mhvtl server chmod u+x 0001-Correct-VPD-updates-for-library-personality-modules.patch execute 0001-Correct-VPD-updates-for-library-personality-modules.patch ./0001-Correct-VPD-updates-for-library-personality-modules.patch is that right? |
Hi, just installed MHVTL 1.5, and after the patch, still see some issues on RHEL6.5, but is better than before, this problem will cause some issues as we where planing to add a second mhvtl device but as the serial is not shown, we have stopped that plan. and my C skills are not good enough to understand how to fix this :(
this is the mhVTL /dev/tape/by-id/scsi-1IBM_3573-TL -> ../../sg15 as you can see , for some reason, udev is not recognizing the serial number, i have the same library model, a physical one, and udev recognize it as /dev/tape/by-id/scsi-1IBM_3573-TL_00X4U78P1300_LL0 -> ../../sg19 page 0x80 show the serial number, while 0x83 did not. [root@backup02 SOURCES]# sg_inq -H -p 0x80 /dev/sg15 VPD INQUIRY, page code=0x80: 00 08 80 00 16 30 30 58 34 55 37 38 50 38 00 00 00 ....00X4U78P8... 10 20 20 20 20 00 00 00 00 00 00 ...... [root@backup02 SOURCES]# sg_inq -H -p 0x83 /dev/sg15 VPD INQUIRY, page code=0x83: 00 08 83 00 32 02 01 00 28 49 42 4d 20 20 20 20 20 ...2...(IBM 10 33 35 37 33 2d 54 4c 20 20 20 20 20 20 20 20 20 3573-TL 20 00 00 00 00 00 00 00 00 00 00 00 00 20 20 20 20 ............ 30 00 00 00 00 00 00 ...... [root@backup02 SOURCES]# sg_inq -H -p 0x80 /dev/sg19 VPD INQUIRY, page code=0x80: 00 08 80 00 10 30 30 58 34 55 37 38 50 31 33 30 30 ....00X4U78P1300 10 5f 4c 4c 30 _LL0 VPD INQUIRY, page code=0x83: 00 08 83 00 2c 02 01 00 28 49 42 4d 20 20 20 20 20 ...,...(IBM 10 33 35 37 33 2d 54 4c 20 20 20 20 20 20 20 20 20 3573-TL 20 30 30 58 34 55 37 38 50 31 33 30 30 5f 4c 4c 30 00X4U78P1300_LL0 |
Administrator
|
Many thanks for the bug report. I'll check into it Sent from my iPhone On 3 Jun 2014, at 3:04, "Marcelo Bartsch [via mhVTL - A Linux Virtual Tape Library]" <[hidden email]> wrote:
Regards from Australia
Mark Harvey |
Administrator
|
In reply to this post by Marcelo Bartsch
I should have a patch for you to test very soon. Sent from my iPhone On 3 Jun 2014, at 3:04, "Marcelo Bartsch [via mhVTL - A Linux Virtual Tape Library]" <[hidden email]> wrote:
Regards from Australia
Mark Harvey |
Administrator
|
In reply to this post by Marcelo Bartsch
Any chance of testing these two patches.. Note: I've now realized this is the wrong way to fix the problem and will be providing another patch shortly.On Tue, Jun 3, 2014 at 5:48 PM, Mark Harvey <[hidden email]> wrote:
![]() ![]()
Regards from Australia
Mark Harvey |
Administrator
|
In reply to this post by Marcelo Bartsch
Just pushed several fixes into github to help/fix the VPD 0x80 & 0x83 page information.
Please let me know if it fixes your problems.
Regards from Australia
Mark Harvey |
Hi Mark,
Thanks for your great MHVTL and support ! After I installed MHVTL 1.5 on an CentOS 6.5 for use by a TSM 5.5 server, I had some issue with serial not showing that caused some problems with TSM. I was unable to use one of the two vtls I've. After applying a first path : 0001-Correct-VPD-updates-for-library-personality-modules.patch, it was better but my L180 was still unusable. I've juste applyied the two more patches : 0001-vtllibrary-Add-missing-serial-number-from-INQUIRY-pa.patch and 0002-Correct-serial-number-length-for-IBM-3100-TS.patch and it seems to work fine with TSM but I still have have a problem with some inquieries (x83 on L180, see below) : # lsscsi -g [0:0:0:0] disk ATA ST9250827AS 3.AH /dev/sda /dev/sg0 [1:0:0:0] cd/dvd MATSHITA DVD-RAM UJ862A SB04 /dev/sr0 /dev/sg1 [7:0:0:0] mediumx IBM 03584L32 0105 - /dev/sg10 [7:0:1:0] tape IBM ULT3580-TD5 0105 - /dev/sg2 [7:0:2:0] tape IBM ULT3580-TD5 0105 - /dev/sg3 [7:0:3:0] tape IBM ULT3580-TD5 0105 - /dev/sg4 [7:0:4:0] tape IBM ULT3580-TD5 0105 - /dev/sg5 [7:0:8:0] mediumx STK L180 0105 /dev/sch0 /dev/sg11 [7:0:9:0] tape STK T10000B 0105 /dev/st0 /dev/sg6 [7:0:10:0] tape STK T10000B 0105 /dev/st1 /dev/sg7 [7:0:11:0] tape STK T10000B 0105 /dev/st2 /dev/sg8 [7:0:12:0] tape STK T10000B 0105 /dev/st3 /dev/sg9 # sg_inq -H -p 0x83 /dev/sg10 VPD INQUIRY, page code=0x83: 00 08 83 00 2c 02 01 00 28 49 42 4d 20 20 20 20 20 ...,...(IBM 10 30 33 35 38 34 4c 33 32 20 20 20 20 20 20 20 20 03584L32 20 4d 48 56 54 4c 5f 41 20 20 20 20 20 30 34 30 00 MHVTL_A 040. # sg_inq -H -p 0x83 /dev/sg11 VPD INQUIRY, page code=0x83: inquiry: failed, res=97 # sg_inq -H -p 0x80 /dev/sg10 VPD INQUIRY, page code=0x80: 00 08 80 00 16 4d 48 56 54 4c 5f 41 20 20 00 00 00 ....MHVTL_A ... 10 30 34 30 00 00 00 00 00 00 00 040....... # sg_inq -H -p 0x80 /dev/sg11 VPD INQUIRY, page code=0x80: 00 08 80 00 12 4d 48 56 54 4c 5f 42 20 20 00 00 00 ....MHVTL_B ... 10 00 00 00 00 00 00
Erwann
|
Administrator
|
The L180 / L700 documentation I have
"L180/L700e Tape Libraries and PTP Interface Reference Manual SCSI and Fibre Channel" (Document 95869) http://docs.oracle.com/cd/E19323-01/en/95869/95869.pdf Documents that only VPD page 0x80 is supported on these libraries. Hence page 0x83 has been removed. If you have updated document that changes this, can you please forward.
Regards from Australia
Mark Harvey |
In reply to this post by Mark Harvey
I'm Testing now! sorry for the delay i was off shift , now back at work
|
Administrator
|
In reply to this post by Mark Harvey
Oh, just thought of something.
Applications should query VPD page 0 to identify if the target supports this page - if they don't want to be surprised by a potential failure. e.g. sg_inq -p 0 /dev/sg11 Only hex output supported. sg_vpd decodes more pages. VPD INQUIRY, page code=0x00: [PQual=0 Peripheral device type: medium changer] Supported VPD pages: 0x0 Supported VPD pages 0x80 Unit serial number 0x83 Device identification 0xc0 vendor: Firmware numbers (seagate); Unit path report (EMC) 0xd0 0xff We can see this device supports VPD pages 0x 80/83/c0/d0 & ff - Any other page should result in an error status.
Regards from Australia
Mark Harvey |
In reply to this post by Mark Harvey
Hi Mark,
Thanks for your answer. In fact, it does not cause any problem that VPD page 0x80 is not supported with L180 as my TSM works with it. It was just a comment I'm using this configuration (TSM + MHVTL) but it was unworkable with L180 since 1.5.0. After I applyed the pathes you provided to fix the problem with the missing serial number, everything seems to be fine again. Thanks
Erwann
|
Administrator
|
Many thanks for the confirmation..
I'll build a new 1.5-2 with these fixes included - sometime in the next week or so (traveling overseas at the moment).
Regards from Australia
Mark Harvey |
Free forum by Nabble | Edit this page |