MHVTL - Linux Virtual Tape Library - Community Forums

MHVTL and TSM : Some error

classic Classic list List threaded Threaded
♦
♦
 34 messages Options
12
crippa.andrea
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

MHVTL and TSM : Some error

crippa.andrea
Hello to all,
first of all : excuse me for my english .......


I'm tryng to install and use mhvtl with scst and Tsm

Mhvtl + scsi and iscst on Linux Centos 5.6 with vanilla kernel 2.6.38

Tsm is on W2K8R2


I've some problem getting tsm + mhvtl working ...

Now i'm tryng beta 0.19-1

device.conf :
Library: 10 CHANNEL: 00 TARGET: 00 LUN: 00
 Vendor identification: IBM
 Product identification: 03584L32
 Product revision level: 4.02
 Unit serial number: 9890400
 NAA: 150:22:33:44:ab:00:00:00

Drive: 14 CHANNEL: 00 TARGET: 04 LUN: 00
 Library ID: 10 Slot: 04
 Vendor identification: IBM
 Product identification: ULT3580-TD4
 Product revision level: 550V
 Unit serial number: XYZZY_A4
 NAA: 10:22:33:44:ab:00:04:00
 Compression: factor 1 enabled 1
 READ_ONLY: LTO1 Data
 READ_ONLY: LTO2 Data
 READ_WRITE: LTO3 Data
 READ_WRITE: LTO4 Data
 WORM: LTO3 Data
 WORM: LTO4 Data
 ENCRYPTION: LTO4 Data

Library.conf
Drive 1:
Drive 2:
Drive 3:
Drive 4:

Picker 1:

MAP 1:
MAP 2:
MAP 3:
MAP 4:

# Slot 1 - ?, no gaps
# Slot N: [barcode]
# [barcode]
# a barcode is comprised of three fields: [Leading] [identifier] [Trailing]
# Leading "CLN" -- cleaning tape
# Leading "W" -- WORM tape
# Leading "NOBAR" -- will appear to have no barcode
# If the barcode is at least 8 character long, then the last two characters are Trailing
# Trailing "S3" - SDLT600
# Trailing "X4" - AIT-4
# Trailing "L1" - LTO 1
# Trailing "TA" - T10000+
# Trailing "JA" - 3592+
# Trailing "JB" - 3592E05+
# Trailing "JW" - WORM 3592+
# Trailing "JX" - WORM 3592E05+
#
Slot 1:
Slot 2:
Slot 3:
Slot 4:
Slot 5:
Slot 6:
Slot 7:
Slot 8:
Slot 9:
Slot 10:
Slot 11:
Slot 12:
Slot 13:
Slot 14:
Slot 15:
Slot 16:
Slot 17:
Slot 18:
Slot 19:
Slot 20:
Slot 21:
Slot 22:
Slot 23:
Slot 24:
Slot 25:
Slot 26:
Slot 27:
Slot 28:
Slot 29:


Library are empty becouse i'm tryng to label some tape with TSM, so ervery test i'll do vtlcmd load map ecc. ecc.


When tryng to label some tape, i'll get this error :

Jul  1 00:24:37 lvtl vtllibrary[4235]: mkSenseBuf: SENSE [Key/ASC/ASCQ] [04 04 03]
Jul  1 00:24:37 lvtl vtllibrary[4235]: CDB (2647) a5 00 01 00 02 00 00 01 00 00 00 00
Jul  1 00:24:37 lvtl vtllibrary[4235]: smc_move_medium: MOVE MEDIUM (2647) **
Jul  1 00:24:37 lvtl vtllibrary[4235]: Moving from slot 512 to Slot 1 using transport 256, Invert media: no
Jul  1 00:24:37 lvtl vtllibrary[4235]: move_slot2drive: About to send cmd: 'lload CR0001L4' to drive 11
Jul  1 00:24:38 lvtl vtltape[4219]: processMessageQ: Q snd_id 10 msg : lload CR0001L4
Jul  1 00:24:38 lvtl vtltape[4219]: loadTape: Media 'LTO4 Data' loaded with S/No. : CR0001L4_1309470375
Jul  1 00:24:38 lvtl vtltape[4219]: mkSenseBuf: SENSE [Key/ASC/ASCQ] [06 28 00]
Jul  1 00:24:38 lvtl vtltape[4219]: loadTape: Previous unload was not clean
Jul  1 00:24:38 lvtl vtltape[4219]: loadTape: Tape capacity: 524288000
Jul  1 00:24:38 lvtl vtltape[4219]: loadTape: Tape CR0001L4 failed to load with type 'LTO4 Data' in drive type 'LTO4'

I don't understand where i've to look for solving my issue.


I've just tried the 0.18-6 version with same config  but i've some other strange error :

Jun 30 23:08:23 lvtl kernel: [0]: __scst_check_blocked_dev:6689:cmd dde77e64 (tag 2013265920, op 12): blocking further cmds on dev 1:0:1:0 due to possible double reset UA
Jun 30 23:08:23 lvtl kernel: [0]: scst_block_dev:6639:Device BLOCK (new count 1), dev 1:0:1:0
Jun 30 23:08:23 lvtl vtltape[9123]: CDB (2565) 12 00 00 00 38 00
Jun 30 23:08:23 lvtl vtltape[9123]: spc_inquiry: INQUIRY ** (2565)
Jun 30 23:08:23 lvtl kernel: [0]: scst_check_unblock_dev:160:cmd dde77e64 (tag 2013265920): unblocking dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: scst_unblock_dev:6716:Device UNBLOCK(new 0), dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: __scst_check_blocked_dev:6689:cmd dde77d1c (tag 2030043136, op 12): blocking further cmds on dev 1:0:1:0 due to possible double reset UA
Jun 30 23:08:23 lvtl kernel: [0]: scst_block_dev:6639:Device BLOCK (new count 1), dev 1:0:1:0
Jun 30 23:08:23 lvtl vtltape[9123]: CDB (2566) 12 20 00 00 38 00
Jun 30 23:08:23 lvtl vtltape[9123]: spc_inquiry: INQUIRY ** (2566)
Jun 30 23:08:23 lvtl kernel: [0]: scst_check_unblock_dev:160:cmd dde77d1c (tag 2030043136): unblocking dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: scst_unblock_dev:6716:Device UNBLOCK(new 0), dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [9505]: scst: scst_parse_cmd:782:Warning: expected transfer length 68 for opcode 0x12 (handler dev_tape, target iscsi) doesn't match decoded value 22
Jun 30 23:08:23 lvtl kernel: [9505]: scst_parse_cmd:784:Suspicious CDB:
Jun 30 23:08:23 lvtl kernel:  (h)___0__1__2__3__4__5__6__7__8__9__A__B__C__D__E__F
Jun 30 23:08:23 lvtl kernel:    0: 12 21 80 00 16 00   .!....
Jun 30 23:08:23 lvtl vtltape[9123]: CDB (2567) 12 21 80 00 16 00
Jun 30 23:08:23 lvtl kernel: [0]: __scst_check_blocked_dev:6689:cmd dde77bd4 (tag 2046820352, op 12): blocking further cmds on dev 1:0:1:0 due to possible double reset UA
Jun 30 23:08:23 lvtl vtltape[9123]: spc_inquiry: INQUIRY ** (2567)
Jun 30 23:08:23 lvtl kernel: [0]: scst_block_dev:6639:Device BLOCK (new count 1), dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: scst_check_unblock_dev:160:cmd dde77bd4 (tag 2046820352): unblocking dev 1:0:1:0
Jun 30 23:08:23 lvtl vtltape[9123]: CDB (2568) 12 21 83 00 40 00
Jun 30 23:08:23 lvtl kernel: [0]: scst_unblock_dev:6716:Device UNBLOCK(new 0), dev 1:0:1:0
Jun 30 23:08:23 lvtl vtltape[9123]: spc_inquiry: INQUIRY ** (2568)
Jun 30 23:08:23 lvtl kernel: [9505]: scst: scst_parse_cmd:782:Warning: expected transfer length 104 for opcode 0x12 (handler dev_tape, target iscsi) doesn't match decoded value 64
Jun 30 23:08:23 lvtl kernel: [9505]: scst_parse_cmd:784:Suspicious CDB:
Jun 30 23:08:23 lvtl kernel:  (h)___0__1__2__3__4__5__6__7__8__9__A__B__C__D__E__F
Jun 30 23:08:23 lvtl kernel:    0: 12 21 83 00 40 00   .!..@.
Jun 30 23:08:23 lvtl kernel: [0]: __scst_check_blocked_dev:6689:cmd dde77a8c (tag 2063597568, op 12): blocking further cmds on dev 1:0:1:0 due to possible double reset UA
Jun 30 23:08:23 lvtl kernel: [0]: scst_block_dev:6639:Device BLOCK (new count 1), dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: scst_check_unblock_dev:160:cmd dde77a8c (tag 2063597568): unblocking dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: scst_unblock_dev:6716:Device UNBLOCK(new 0), dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: __scst_check_blocked_dev:6689:cmd dde77944 (tag 2399141888, op 12): blocking further cmds on dev 1:0:2:0 due to possible double reset UA
Jun 30 23:08:23 lvtl kernel: [0]: scst_block_dev:6639:Device BLOCK (new count 1), dev 1:0:2:0
Jun 30 23:08:23 lvtl vtltape[9127]: CDB (2569) 12 00 00 00 38 00
Jun 30 23:08:23 lvtl vtltape[9127]: spc_inquiry: INQUIRY ** (2569)


Thanks in advance for any reply
Yasuhisa Ishikawa
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

Yasuhisa Ishikawa
By the message "Previous unload was not clean", I assume that drive type is illegal.
Replace "LTOx Data" with "LTOx" in device.conf and restart mhvtl.
Yasuhisa Ishikawa
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

Yasuhisa Ishikawa
In reply to this post by crippa.andrea
For your later case, errors occured in scst side.
I suppose that you exposed tape drives as block devices(disks). Review scst.conf and /proc/scsi_tgt/scsi_tgt.
Mark Harvey
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

Mark Harvey
In reply to this post by crippa.andrea
crippa.andrea wrote
I'm tryng to install and use mhvtl with scst and Tsm

Mhvtl + scsi and iscst on Linux Centos 5.6 with vanilla kernel 2.6.38

Tsm is on W2K8R2

I've some problem getting tsm + mhvtl working ...

Now i'm tryng beta 0.19-1
Please don't. Use the 0.18 branch instead.
I've not updated the 0.19 for quite a while and many fixes are in the 0.18-17 that have not been back-ported to the 0.19 branch.
The 0.19 branch was to use an xml config file instead of the various custom config files used. I've not had the time to address the xml conversion for a while now.

It is something I need to address.

crippa.andrea wrote
device.conf :
Library: 10 CHANNEL: 00 TARGET: 00 LUN: 00
 Vendor identification: IBM
 Product identification: 03584L32
 Product revision level: 4.02
 Unit serial number: 9890400
 NAA: 150:22:33:44:ab:00:00:00

Drive: 14 CHANNEL: 00 TARGET: 04 LUN: 00
 Library ID: 10 Slot: 04
 Vendor identification: IBM
 Product identification: ULT3580-TD4
 Product revision level: 550V
 Unit serial number: XYZZY_A4
 NAA: 10:22:33:44:ab:00:04:00
 Compression: factor 1 enabled 1
 READ_ONLY: LTO1 Data
 READ_ONLY: LTO2 Data
 READ_WRITE: LTO3 Data
 READ_WRITE: LTO4 Data
 WORM: LTO3 Data
 WORM: LTO4 Data
 ENCRYPTION: LTO4 Data
Those media mount rules are incorrect.
They should look like:
 READ_ONLY: LTO1
 READ_ONLY: LTO2
 READ_WRITE: LTO3
 READ_WRITE: LTO4

However - for trouble-shooting purposes, remove all mount rules, and re-start mhvtl daemons.

crippa.andrea wrote
I've just tried the 0.18-6 version with same config  but i've some other strange error :

Jun 30 23:08:23 lvtl kernel: [0]: __scst_check_blocked_dev:6689:cmd dde77e64 (tag 2013265920, op 12): blocking further cmds on dev 1:0:1:0 due to possible double reset UA
Jun 30 23:08:23 lvtl kernel: [0]: scst_block_dev:6639:Device BLOCK (new count 1), dev 1:0:1:0
Jun 30 23:08:23 lvtl vtltape[9123]: CDB (2565) 12 00 00 00 38 00
Jun 30 23:08:23 lvtl vtltape[9123]: spc_inquiry: INQUIRY ** (2565)
Jun 30 23:08:23 lvtl kernel: [0]: scst_check_unblock_dev:160:cmd dde77e64 (tag 2013265920): unblocking dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: scst_unblock_dev:6716:Device UNBLOCK(new 0), dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: __scst_check_blocked_dev:6689:cmd dde77d1c (tag 2030043136, op 12): blocking further cmds on dev 1:0:1:0 due to possible double reset UA
Jun 30 23:08:23 lvtl kernel: [0]: scst_block_dev:6639:Device BLOCK (new count 1), dev 1:0:1:0
Jun 30 23:08:23 lvtl vtltape[9123]: CDB (2566) 12 20 00 00 38 00
Jun 30 23:08:23 lvtl vtltape[9123]: spc_inquiry: INQUIRY ** (2566)
Jun 30 23:08:23 lvtl kernel: [0]: scst_check_unblock_dev:160:cmd dde77d1c (tag 2030043136): unblocking dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: scst_unblock_dev:6716:Device UNBLOCK(new 0), dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [9505]: scst: scst_parse_cmd:782:Warning: expected transfer length 68 for opcode 0x12 (handler dev_tape, target iscsi) doesn't match decoded value 22
Jun 30 23:08:23 lvtl kernel: [9505]: scst_parse_cmd:784:Suspicious CDB:
Jun 30 23:08:23 lvtl kernel:  (h)___0__1__2__3__4__5__6__7__8__9__A__B__C__D__E__F
Jun 30 23:08:23 lvtl kernel:    0: 12 21 80 00 16 00   .!....
Jun 30 23:08:23 lvtl vtltape[9123]: CDB (2567) 12 21 80 00 16 00
Jun 30 23:08:23 lvtl kernel: [0]: __scst_check_blocked_dev:6689:cmd dde77bd4 (tag 2046820352, op 12): blocking further cmds on dev 1:0:1:0 due to possible double reset UA
Jun 30 23:08:23 lvtl vtltape[9123]: spc_inquiry: INQUIRY ** (2567)
Jun 30 23:08:23 lvtl kernel: [0]: scst_block_dev:6639:Device BLOCK (new count 1), dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: scst_check_unblock_dev:160:cmd dde77bd4 (tag 2046820352): unblocking dev 1:0:1:0
Jun 30 23:08:23 lvtl vtltape[9123]: CDB (2568) 12 21 83 00 40 00
Jun 30 23:08:23 lvtl kernel: [0]: scst_unblock_dev:6716:Device UNBLOCK(new 0), dev 1:0:1:0
Jun 30 23:08:23 lvtl vtltape[9123]: spc_inquiry: INQUIRY ** (2568)
Jun 30 23:08:23 lvtl kernel: [9505]: scst: scst_parse_cmd:782:Warning: expected transfer length 104 for opcode 0x12 (handler dev_tape, target iscsi) doesn't match decoded value 64
Jun 30 23:08:23 lvtl kernel: [9505]: scst_parse_cmd:784:Suspicious CDB:
Jun 30 23:08:23 lvtl kernel:  (h)___0__1__2__3__4__5__6__7__8__9__A__B__C__D__E__F
Jun 30 23:08:23 lvtl kernel:    0: 12 21 83 00 40 00   .!..@.
Jun 30 23:08:23 lvtl kernel: [0]: __scst_check_blocked_dev:6689:cmd dde77a8c (tag 2063597568, op 12): blocking further cmds on dev 1:0:1:0 due to possible double reset UA
Jun 30 23:08:23 lvtl kernel: [0]: scst_block_dev:6639:Device BLOCK (new count 1), dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: scst_check_unblock_dev:160:cmd dde77a8c (tag 2063597568): unblocking dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: scst_unblock_dev:6716:Device UNBLOCK(new 0), dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: __scst_check_blocked_dev:6689:cmd dde77944 (tag 2399141888, op 12): blocking further cmds on dev 1:0:2:0 due to possible double reset UA
Jun 30 23:08:23 lvtl kernel: [0]: scst_block_dev:6639:Device BLOCK (new count 1), dev 1:0:2:0
Jun 30 23:08:23 lvtl vtltape[9127]: CDB (2569) 12 00 00 00 38 00
Jun 30 23:08:23 lvtl vtltape[9127]: spc_inquiry: INQUIRY ** (2569)


Thanks in advance for any reply
This SCST issue has been commented on, in another response.

Cheers
crippa.andrea
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

crippa.andrea
Mark Harvey wrote
Please don't. Use the 0.18 branch instead.
I've not updated the 0.19 for quite a while and many fixes are in the 0.18-17 that have not been back-ported to the 0.19 branch.
The 0.19 branch was to use an xml config file instead of the various custom config files used. I've not had the time to address the xml conversion for a while now.

It is something I need to address.
Ok, ill try to install and configure 0.18-17 wich is newer than the release i've used

crippa.andrea wrote
Drive: 14 CHANNEL: 00 TARGET: 04 LUN: 00
 Library ID: 10 Slot: 04
 Vendor identification: IBM
 Product identification: ULT3580-TD4
 Product revision level: 550V
 Unit serial number: XYZZY_A4
 NAA: 10:22:33:44:ab:00:04:00
 Compression: factor 1 enabled 1
 READ_ONLY: LTO1 Data
 READ_ONLY: LTO2 Data
 READ_WRITE: LTO3 Data
 READ_WRITE: LTO4 Data
 WORM: LTO3 Data
 WORM: LTO4 Data
 ENCRYPTION: LTO4 Data
Mark Harvey wrote
Those media mount rules are incorrect.
They should look like:
 READ_ONLY: LTO1
 READ_ONLY: LTO2
 READ_WRITE: LTO3
 READ_WRITE: LTO4

However - for trouble-shooting purposes, remove all mount rules, and re-start mhvtl daemons.
Yes, my running config before 0.19-1 was with "LTO1" - "LTO4" and not with "LTO1 Data" ecc. ecc. ..... it was just a try




crippa.andrea wrote
I've just tried the 0.18-6 version with same config  but i've some other strange error :

Jun 30 23:08:23 lvtl kernel: [0]: __scst_check_blocked_dev:6689:cmd dde77e64 (tag 2013265920, op 12): blocking further cmds on dev 1:0:1:0 due to possible double reset UA
Jun 30 23:08:23 lvtl kernel: [0]: scst_block_dev:6639:Device BLOCK (new count 1), dev 1:0:1:0
Jun 30 23:08:23 lvtl vtltape[9123]: CDB (2565) 12 00 00 00 38 00
Jun 30 23:08:23 lvtl vtltape[9123]: spc_inquiry: INQUIRY ** (2565)
Jun 30 23:08:23 lvtl kernel: [0]: scst_check_unblock_dev:160:cmd dde77e64 (tag 2013265920): unblocking dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: scst_unblock_dev:6716:Device UNBLOCK(new 0), dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: __scst_check_blocked_dev:6689:cmd dde77d1c (tag 2030043136, op 12): blocking further cmds on dev 1:0:1:0 due to possible double reset UA
Jun 30 23:08:23 lvtl kernel: [0]: scst_block_dev:6639:Device BLOCK (new count 1), dev 1:0:1:0
Jun 30 23:08:23 lvtl vtltape[9123]: CDB (2566) 12 20 00 00 38 00
Jun 30 23:08:23 lvtl vtltape[9123]: spc_inquiry: INQUIRY ** (2566)
Jun 30 23:08:23 lvtl kernel: [0]: scst_check_unblock_dev:160:cmd dde77d1c (tag 2030043136): unblocking dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: scst_unblock_dev:6716:Device UNBLOCK(new 0), dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [9505]: scst: scst_parse_cmd:782:Warning: expected transfer length 68 for opcode 0x12 (handler dev_tape, target iscsi) doesn't match decoded value 22
Jun 30 23:08:23 lvtl kernel: [9505]: scst_parse_cmd:784:Suspicious CDB:
Jun 30 23:08:23 lvtl kernel:  (h)___0__1__2__3__4__5__6__7__8__9__A__B__C__D__E__F
Jun 30 23:08:23 lvtl kernel:    0: 12 21 80 00 16 00   .!....
Jun 30 23:08:23 lvtl vtltape[9123]: CDB (2567) 12 21 80 00 16 00
Jun 30 23:08:23 lvtl kernel: [0]: __scst_check_blocked_dev:6689:cmd dde77bd4 (tag 2046820352, op 12): blocking further cmds on dev 1:0:1:0 due to possible double reset UA
Jun 30 23:08:23 lvtl vtltape[9123]: spc_inquiry: INQUIRY ** (2567)
Jun 30 23:08:23 lvtl kernel: [0]: scst_block_dev:6639:Device BLOCK (new count 1), dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: scst_check_unblock_dev:160:cmd dde77bd4 (tag 2046820352): unblocking dev 1:0:1:0
Jun 30 23:08:23 lvtl vtltape[9123]: CDB (2568) 12 21 83 00 40 00
Jun 30 23:08:23 lvtl kernel: [0]: scst_unblock_dev:6716:Device UNBLOCK(new 0), dev 1:0:1:0
Jun 30 23:08:23 lvtl vtltape[9123]: spc_inquiry: INQUIRY ** (2568)
Jun 30 23:08:23 lvtl kernel: [9505]: scst: scst_parse_cmd:782:Warning: expected transfer length 104 for opcode 0x12 (handler dev_tape, target iscsi) doesn't match decoded value 64
Jun 30 23:08:23 lvtl kernel: [9505]: scst_parse_cmd:784:Suspicious CDB:
Jun 30 23:08:23 lvtl kernel:  (h)___0__1__2__3__4__5__6__7__8__9__A__B__C__D__E__F
Jun 30 23:08:23 lvtl kernel:    0: 12 21 83 00 40 00   .!..@.
Jun 30 23:08:23 lvtl kernel: [0]: __scst_check_blocked_dev:6689:cmd dde77a8c (tag 2063597568, op 12): blocking further cmds on dev 1:0:1:0 due to possible double reset UA
Jun 30 23:08:23 lvtl kernel: [0]: scst_block_dev:6639:Device BLOCK (new count 1), dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: scst_check_unblock_dev:160:cmd dde77a8c (tag 2063597568): unblocking dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: scst_unblock_dev:6716:Device UNBLOCK(new 0), dev 1:0:1:0
Jun 30 23:08:23 lvtl kernel: [0]: __scst_check_blocked_dev:6689:cmd dde77944 (tag 2399141888, op 12): blocking further cmds on dev 1:0:2:0 due to possible double reset UA
Jun 30 23:08:23 lvtl kernel: [0]: scst_block_dev:6639:Device BLOCK (new count 1), dev 1:0:2:0
Jun 30 23:08:23 lvtl vtltape[9127]: CDB (2569) 12 00 00 00 38 00
Jun 30 23:08:23 lvtl vtltape[9127]: spc_inquiry: INQUIRY ** (2569)

Thanks in advance for any reply
Mark Harvey wrote
This SCST issue has been commented on, in another response.

Cheers

I'm not familiar with scst ......

this is my scst.conf ..... do you see anything worng ?

[HANDLER changer]
DEVICE 2:0:0:0
[HANDLER tape]
DEVICE 2:0:1:0
DEVICE 2:0:2:0
DEVICE 2:0:3:0
DEVICE 2:0:4:0
[GROUP Default_iqn.2010-05.mhvtl:2:0:0:0]
[GROUP Default_iqn.2010-05.mhvtl:2:0:1:0]
[GROUP Default_iqn.2010-05.mhvtl:2:0:2:0]
[GROUP Default_iqn.2010-05.mhvtl:2:0:3:0]
[GROUP Default_iqn.2010-05.mhvtl:2:0:4:0]
[ASSIGNMENT Default_iqn.2010-05.mhvtl:2:0:0:0]
DEVICE 2:0:0:0,0
[ASSIGNMENT Default_iqn.2010-05.mhvtl:2:0:1:0]
DEVICE 2:0:1:0,0
[ASSIGNMENT Default_iqn.2010-05.mhvtl:2:0:2:0]
DEVICE 2:0:2:0,0
[ASSIGNMENT Default_iqn.2010-05.mhvtl:2:0:3:0]
DEVICE 2:0:3:0,0
[ASSIGNMENT Default_iqn.2010-05.mhvtl:2:0:4:0]
DEVICE 2:0:4:0,0

Thanks in advance
Yasuhisa Ishikawa
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

Yasuhisa Ishikawa
Can you post output of "cat /proc/scsi_tgt/scsi_tgt"?
crippa.andrea
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

crippa.andrea
This post was updated on .
Yasuhisa Ishikawa wrote
Can you post output of "cat /proc/scsi_tgt/scsi_tgt"?
[root@lvtl ~]# cat /proc/scsi_tgt/scsi_tgt
Device (host:ch:id:lun or name)                             Device handler
0:0:0:0                                                     none
0:0:1:0                                                     none
1:0:1:0                                                     dev_tape
1:0:2:0                                                     dev_tape
1:0:3:0                                                     dev_tape
1:0:4:0                                                     dev_tape
1:0:0:0                                                     dev_changer

and this is the new associated scst.conf :
[root@lvtl ~]# cat /etc/scst.conf
[HANDLER changer]
DEVICE 1:0:0:0
[HANDLER tape]
DEVICE 1:0:1:0
DEVICE 1:0:2:0
DEVICE 1:0:3:0
DEVICE 1:0:4:0
[GROUP Default_iqn.2010-05.mhvtl:1:0:0:0]
[GROUP Default_iqn.2010-05.mhvtl:1:0:1:0]
[GROUP Default_iqn.2010-05.mhvtl:1:0:2:0]
[GROUP Default_iqn.2010-05.mhvtl:1:0:3:0]
[GROUP Default_iqn.2010-05.mhvtl:1:0:4:0]
[ASSIGNMENT Default_iqn.2010-05.mhvtl:1:0:0:0]
DEVICE 1:0:0:0,0
[ASSIGNMENT Default_iqn.2010-05.mhvtl:1:0:1:0]
DEVICE 1:0:1:0,0
[ASSIGNMENT Default_iqn.2010-05.mhvtl:1:0:2:0]
DEVICE 1:0:2:0,0
[ASSIGNMENT Default_iqn.2010-05.mhvtl:1:0:3:0]
DEVICE 1:0:3:0,0
[ASSIGNMENT Default_iqn.2010-05.mhvtl:1:0:4:0]
DEVICE 1:0:4:0,0


crippa.andrea
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

crippa.andrea
Hi, I've newly configured the version 0.18-7

This is the log of a LABEL LIBVOLUME process of TSM ... se the attached below :
log.txt

The effect on the TSM side is that the Tape is labelled, but when try to write somethings to it it will be turned to private becouse the TSM cannot write any data on it.

Thanks in advance


Crippa Andrea
nia
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

nia
Administrator
crippa.andrea,

Hello

I am trying to reproduce the same error on my system.

Can you post all commands exactly as entered in both mhvtl and TSM ?

Also configuration information about your TSM.

TSM version
TSM error
q library f=d
q devc f=d
q libv f=d
show slots "library_name"

Thanks

nia
crippa.andrea
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

crippa.andrea
This post was updated on .
nia wrote
crippa.andrea,

Hello

I am trying to reproduce the same error on my system.

Can you post all commands exactly as entered in both mhvtl and TSM ?

Also configuration information about your TSM.

TSM version
TSM error
q library f=d
q devc f=d
q libv f=d
show slots "library_name"

Thanks

nia
Hello, here you are the information required ....


TSM version 5,5,5 on W2K8R2
MHVTL, SCST and iSCST on Linux CentOS 5.6 with Vanilla 2.6.38 patched for scst.

And now ... some files .....
ACTLOG.TXT
MESSAGES.TXT
SHSLOT.TXT
LIBVOL.TXT
DEVCLASS.TXT
LIBRARY.TXT

Thanks in adavnce

Crippa Andrea

P.S. : This is the command used for the minimal system configuration of Library and Drives

DEFINE Library 3573TL libtype=scsi serial=9890400 AutoLabel=yes RelabelScratch=yes
DEFINE PATH TSMSERVER_SERVER1 3573TL SRCType=SERVER DESTType=LIBRary Device=lb0.0.0.3 ONLine=yes
DEFINE drive 3573TL drive1 serial=XYZZY_A1 element=1 online=yes
DEFINE drive 3573TL drive2 serial=XYZZY_A2 element=2 online=yes
DEFINE drive 3573TL drive3 serial=XYZZY_A3 element=3 online=yes
DEFINE drive 3573TL drive4 serial=XYZZY_A4 element=4 online=yes
DEFINE PATH TSMSERVER_SERVER1 drive1 SRCType=SERVER DESTType=drive LIBRary=3573TL Device=mt1.0.0.3 ONLine=yes
DEFINE PATH TSMSERVER_SERVER1 drive2 SRCType=SERVER DESTType=drive LIBRary=3573TL Device=mt2.0.0.3 ONLine=yes
DEFINE PATH TSMSERVER_SERVER1 drive3 SRCType=SERVER DESTType=drive LIBRary=3573TL Device=mt3.0.0.3 ONLine=yes
DEFINE PATH TSMSERVER_SERVER1 drive4 SRCType=SERVER DESTType=drive LIBRary=3573TL Device=mt4.0.0.3 ONLine=yes
nia
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

nia
Administrator
TSM error:

07/01/2011 14:16:21      ANR9999D_0521343731 (pvrntp.c:1293) Thread<26>: Could not
                          determine media type, rc = 1 (SESSION: 93, PROCESS: 9)  




Odd .. I thought this was fixed already .. see

http://mhvtl-linux-virtual-tape-library-community-forums.966029.n3.nabble.com/TSM-Could-not-determine-media-type-LTO-4-tp2783699p2783699.html

I will look into it further ..

nia
crippa.andrea
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

crippa.andrea
In reply to this post by crippa.andrea
Hello to all ...

this evening I've update scst to latest version 2.0.0.1 (3646) and played with the scst configuration files.....

The problem is still the same ....

ACTLOG.TXT
messages.txt

Some notices :

scst.conf and is very different ....
scst.conf.txt
iscsi-scstd.conf.txt

mhvtl configuration remain unchanged :
device.conf.txt.txt
library_contents.10.txt

I've no more /proc/scsi_tgt/scsi_tgt .... is this ok ?
By the way .... scst and iscsi-scst work as expected and I'm able to pass the target to my windows hosts.

Any help much be appreciated !!!!!

TIA
crippa.andrea
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

crippa.andrea
In reply to this post by nia
nia wrote
TSM error:

07/01/2011 14:16:21      ANR9999D_0521343731 (pvrntp.c:1293) Thread<26>: Could not
                          determine media type, rc = 1 (SESSION: 93, PROCESS: 9)  




Odd .. I thought this was fixed already .. see

http://mhvtl-linux-virtual-tape-library-community-forums.966029.n3.nabble.com/TSM-Could-not-determine-media-type-LTO-4-tp2783699p2783699.html

I will look into it further ..

nia
Yes nia .... i've just looked at this tread ..... but i've got the same error ..... so ...

1) - This is a regression (couse i'm using mhvtl 0.18-17 and seems that was fixed on 0.18-15)
2) - My config is different from that one


Nia ... have you got a system with mhvyl + tsm ..... what is your config (waht distro + kernel + mhvtl ver + scst ver + tsm ver ) ?
Have you got any problem like mine ?

TIA

Mark Harvey
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

Mark Harvey
crippa.andrea wrote
Jul  1 21:04:46 lvtl vtltape[4565]: CDB (482) 12 20 00 00 38 00
Jul  1 21:04:46 lvtl vtltape[4565]: spc_inquiry: INQUIRY ** (482)
Jul  1 21:04:46 lvtl kernel: [0]: scst_check_unblock_dev:160:cmd ddfdde90 (tag 419430400): unblocking dev 1:0:3:0
Jul  1 21:04:46 lvtl kernel: [0]: scst_unblock_dev:6594:Device UNBLOCK(new 0), dev 1:0:3:0
Jul  1 21:04:46 lvtl kernel: [4627]: scst: scst_parse_cmd:780:Warning: expected transfer length 68 for opcode 0x12 (handler dev_tape, target iscsi) doesn't match decoded value 22
Looks really strange..

The length in the 'inquiry' (as specified by the initiator) is bytes cdb[3] << 8 | cdb[4]
Hence is 0038 (hex) => 56 Decimal.

I have no idea where scst is getting value length of 68 from.
Or for that matter what the statement 'doesn't match decoded value 22' refers to.

Any chance of running:

# sg_raw -r 56 /dev/sg10 12 20 00 00 38 00 (update /dev/sg10 to suit your setup)


As a reference, my returned data is:
mharvey02:~ # sg_raw -r 56 /dev/sg10 12 20 00 00 38 00
SCSI Status: Good

Sense Information:
sense buffer empty

Received 56 bytes of data:
 00     01 80 05 42 3d 00 00 02  49 42 4d 20 20 20 20 20    ...B=...IBM
 10     55 4c 54 33 35 38 30 2d  54 44 34 20 20 20 20 20    ULT3580-TD4
 20     35 35 30 56 00 00 00 00  00 00 00 00 00 00 00 00    550V............
 30     00 00 00 00 00 00 00 00                             ........
nia
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

nia
Administrator
This post was updated on .
In reply to this post by crippa.andrea
Did you investigate this if to be the case ?

Windows drivers

https://www-304.ibm.com/support/docview.wss?uid=swg21438456

I have not tested heavily recently but since 18-15, I think , I thought I had all of my TSM issues revolved then.

As of right now, I can confirm that LTO1 works but not sure about LTO4 or 5 if they still work .. My installation/config is no longer the same. I will have to reconfigure and test again.


As far as my config is as the following:

Enterprise Linux Server release 5.6 (Carthage) with Vanilla Kernel  2.6.33.7 recompiled using scst 2.0 SVN 3177 with both Qlogic FC and iSCSI patches

Running TSM Linux/i386 - Version 5, Release 5, Level 5.0 on the same box, but have TSM storage agents running on Solaris Express 11 connecting via FC and on another Linux System via iSCSI along with some NetWorker also.

Using more recent mhvtl code via $ git pull http://github.com/markh794/mhvtl.git

[7:1:0:0]    mediumx IBM      03584L32         4.02  -          /dev/sg17
[7:1:0:1]    tape    IBM      ULT3580-TD1      16E0  -          /dev/sg1
[7:1:0:2]    tape    IBM      ULT3580-TD1      16E0  -          /dev/sg2
[7:1:0:3]    tape    IBM      ULT3580-TD1      16E0  -          /dev/sg3
[7:1:0:4]    tape    IBM      ULT3580-TD1      16E0  -          /dev/sg4
[7:1:0:5]    tape    IBM      ULT3580-TD1      16E0  -          /dev/sg5
[7:1:0:6]    tape    IBM      ULT3580-TD1      16E0  -          /dev/sg6
[7:1:0:7]    tape    IBM      ULT3580-TD1      16E0  -          /dev/sg7
[7:2:0:0]    mediumx IBM      03584L22         4.02  -          /dev/sg18
[7:2:0:1]    tape    IBM      ULT3580-TD5      A3K6  -          /dev/sg8
[7:2:0:2]    tape    IBM      ULT3580-TD5      A3K6  -          /dev/sg9
[7:3:0:0]    mediumx STK      L700             3.18  /dev/sch0  /dev/sg19
[7:3:0:1]    tape    STK      T9840B           1.29  /dev/st0   /dev/sg10
[7:3:0:2]    tape    STK      T9840B           1.29  /dev/st1   /dev/sg11
[7:4:0:0]    mediumx IBM      03584L32         4.02  -          /dev/sg20
[7:4:0:1]    tape    IBM      ULT3580-TD4      4C17  -          /dev/sg12
[7:4:0:2]    tape    IBM      ULT3580-TD4      4C17  -          /dev/sg13
[7:5:0:0]    mediumx IBM      03584L22         4.02  -          /dev/sg21
[7:5:0:1]    tape    IBM      ULT3580-TD3      6430  -          /dev/sg14
[7:5:0:2]    tape    IBM      ULT3580-TD3      6430  -          /dev/sg15
[7:5:0:3]    tape    IBM      ULT3580-TD3      6430  -          /dev/sg16





~ # more /etc/scst.conf

HANDLER dev_changer {
    DEVICE 7:2:0:0
    DEVICE 7:3:0:0
    DEVICE 7:4:0:0
}
HANDLER dev_tape {
    DEVICE 7:2:0:1
    DEVICE 7:2:0:2
    DEVICE 7:1:0:1
    DEVICE 7:1:0:2
    DEVICE 7:1:0:6
    DEVICE 7:1:0:7
    DEVICE 7:4:0:1
    DEVICE 7:4:0:2
    DEVICE 7:3:0:1
    DEVICE 7:3:0:2
}

TARGET_DRIVER qla2x00t {
    TARGET 21:00:00:e0:8b:12:5c:69 {
            LUN 0 7:4:0:0
            LUN 1 7:4:0:1
            LUN 2 7:4:0:2
            LUN 3 7:1:0:1
            LUN 4 7:1:0:6
            enabled 1
     }
     TARGET 21:01:00:e0:8b:32:5c:69 {
            LUN 0 7:2:0:0
            LUN 1 7:2:0:1
            LUN 2 7:2:0:2
            LUN 3 7:1:0:2
            LUN 4 7:1:0:7
            enabled 1
     }
}


TARGET_DRIVER iscsi {
      enabled 1
      TARGET iqn.2009-05.us.nimsa:bdxur:7:1:t {
            LUN 1 7:1:0:6
            LUN 2 7:1:0:7
           enabled 0
      }
      TARGET iqn.2009-05.us.nimsa:bdxur:7:3:t {
            LUN 0 7:3:0:0
            LUN 1 7:3:0:1
            LUN 2 7:3:0:2
           enabled 1
      }
}



crippa.andrea
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

crippa.andrea
nia wrote
Did you investigate this if to be the case ?

Windows drivers

https://www-304.ibm.com/support/docview.wss?uid=swg21438456
Hello ....
I'm investigating the driver ....

Seems that i'm using Windows drivers instead of IBM driver.


Let me try IBM driver ..... i will post the update here.
crippa.andrea
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

crippa.andrea
I've loaded the IBM w08 x64 driver version 6216
Now i'm going into crash issue :

Message from syslogd@ at Sat Jul  2 08:23:15 2011 ...
lvtl kernel: Oops: 0000 [#1] SMP

Message from syslogd@ at Sat Jul  2 08:23:15 2011 ...
lvtl kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:11.0/0000:02:00.0/                                                                             irq

Message from syslogd@ at Sat Jul  2 08:23:15 2011 ...
lvtl kernel: Process 1:0:4:00_0 (pid: 3685, ti=deed8000 task=daae1a10 task.ti=de                                                                             ed8000)

Message from syslogd@ at Sat Jul  2 08:23:15 2011 ...
lvtl kernel: Stack:

Message from syslogd@ at Sat Jul  2 08:23:15 2011 ...
lvtl kernel: Call Trace:

Message from syslogd@ at Sat Jul  2 08:23:15 2011 ...
lvtl kernel: Code: 83 c9 40 56 53 83 ec 04 8b 74 24 14 c7 46 2c 01 00 00 00 89 4                                                                             e 24 c7 46 30 00 00 00 00 c7 46 14 00 00 00 00 c7 46 1c 00 00 00 00 <80> 3a 2f 7                                                                             5 52 64 a1 cc d4 84 c0 8b 98 58 03 00 00 e8 4b 96 00

Message from syslogd@ at Sat Jul  2 08:23:15 2011 ...
lvtl kernel: EIP: [<c04acc5b>] path_init_rcu+0x2c/0x158 SS:ESP 0068:deed9dc0

Message from syslogd@ at Sat Jul  2 08:23:15 2011 ...
lvtl kernel: CR2: 0000000000000000

Here you are some detail :
ACTLOG.TXT
trace.txt
messages.txt
crippa.andrea
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

crippa.andrea
Haha ... nia ... I find you on every post ....

Seems that this crash is not new , according to this thread ....

In the post you've write that you have not the same problem ... are you using Windows with iscsi initiator in that config ?
And are you using the IBM driver ?
 
Today I can try to build a new VM with vanilla kernel 2.6.33.7 according to your post , and build scst and mhvtl based on that kernel .... then test if I've got the problem anymore .....

Let me know about your configuration ('iscsi + windows' or not)

Many Thanks
Mark Harvey
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

Mark Harvey
Any chance of testing a T10000B drive type instead ?

And/or stgt scsi target code ?

The stack trace all looks to be SCST and persistent scsi reservation. So a different driver ( e.g. T10000B) or different scsi-target could help isolate the error. 

Sent from my iPad

On Jul 2, 2011, at 19:55, "crippa.andrea [via MHVTL - Linux Virtual Tape Library - CommunityForums]" <[hidden email]> wrote:

Haha ... nia ... I find you on every post ....

Seems that this crash is not new , according to this thread ....

In the post you've write that you have not the same problem ... are you using Windows with iscsi initiator in that config ?
And are you using the IBM driver ?
 
Today I can try to build a new VM with vanilla kernel 2.6.33.7 according to your post , and build scst and mhvtl based on that kernel .... then test if I've got the problem anymore .....

Let me know about your configuration ('iscsi + windows' or not)

Many Thanks

To start a new topic under MHVTL - Linux Virtual Tape Library - Community Forums, email [hidden email]
To unsubscribe from MHVTL - Linux Virtual Tape Library - Community Forums, click here.
crippa.andrea
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

Re: MHVTL and TSM : Some error

crippa.andrea
Mark Harvey wrote
Any chance of testing a T10000B drive type instead ?
T1000B is not IBM drive, and as far as i know TSM request with IBM changer the use of IBM tape.
But I will give it a try ......

Mark Harvey wrote
And/or stgt scsi target code ?

The stack trace all looks to be SCST and persistent scsi reservation. So a different driver ( e.g. T10000B) or different scsi-target could help isolate the error.
What exactly do yuo want that i do ... I don't understand ....

Thank you
12
Loading...
Powered by Nabble See how NAML generates this page