TSM does not like my mhvtl cleaning tape

[nia]

Hi Mark, and everyone

I am attempting to clean my drives using TSM for the first time with mhvtl..

I have a cleaning tape with Barcode CLN200L4 available in my library.

After issuing tsm "CLEAN DRIVE  03584L32 DRIVE1"

TSM complains with following:

The cartridge in storage element 1223 in library 03584L32 is not a cleaner cartridge as was expected

TSM knows the cartridge that was used is indeed CLN200L4

along with

ANR8302E I/O error on drive DRIVE1 (/dev/IBMtape14) with
                          volume CLN200L4 (OP=READ, Error Number=5, CC=0, rc = 1,
                          KEY=02, ASC=30, ASCQ=03, SENSE=F0.00.02.00.00.00.00.58.0-
                          0.00.00.00.30.03.00.00.00.00.00.00.00.00.00.00.00.00.00.-
                          00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00-
                          .00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.0-
                          0.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.-
                          00.00.00.00.00.00.00.00.00.00.00.00.00, Description=An
                          undetermined error has occurred)

mhvtl dump_tape shows:

PCL is : CLN200L4
Media density code: 0x46
Media type code   : 0x08
Media description : Ultrium 4/16T
Tape Capacity     : 2097152000
Total num of filemarks: 0
Hdr:      End of Data(05), sz             0, Blk No.: 0, data 0

What am I missing ? Did I use the incorrect Barcode format for a cleaner tape ?

[7:6:0:0]    mediumx IBM      03584L32         4.02  -          /dev/sg31
[7:6:0:1]    tape    IBM      ULT3580-TD4      252D  -          /dev/sg17
[7:6:0:2]    tape    IBM      ULT3580-TD4      252D  -          /dev/sg18
[7:6:0:3]    tape    IBM      ULT3580-TD4      252D  -          /dev/sg19
[7:6:0:4]    tape    IBM      ULT3580-TD4      252D  -          /dev/sg20
[7:6:0:5]    tape    IBM      ULT3580-TD4      252D  -          /dev/sg21

Library: 70 CHANNEL: 6 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:6:00:00

Drive: 71 CHANNEL: 6 TARGET: 00 LUN: 01
 Library ID: 70 Slot: 01
 Vendor identification: IBM
 Product identification: ULT3580-TD4
 Product revision level: 252D
 Unit serial number: 70000071
 NAA: 70:11:22:33:ab:6:00:01
 Compression: factor 1 enabled 0

Drive: 72 CHANNEL: 6 TARGET: 00 LUN: 2
 Library ID: 70 Slot: 2
 Vendor identification: IBM
 Product identification: ULT3580-TD4
 Product revision level: 252D
 Unit serial number: 70000072
 NAA: 70:11:22:33:ab:6:00:2
 Compression: factor 1 enabled 0

Drive: 73 CHANNEL: 6 TARGET: 00 LUN: 3
 Library ID: 70 Slot: 3
 Vendor identification: IBM
 Product identification: ULT3580-TD4
 Product revision level: 252D
 Unit serial number: 70000073
 NAA: 70:11:22:33:ab:6:00:3
 Compression: factor 1 enabled 0

Drive: 74 CHANNEL: 6 TARGET: 00 LUN: 4
 Library ID: 70 Slot: 4
 Vendor identification: IBM
 Product identification: ULT3580-TD4
 Product revision level: 252D
 Unit serial number: 70000074
 NAA: 70:11:22:33:ab:6:00:4
 Compression: factor 1 enabled 0

Drive: 75 CHANNEL: 6 TARGET: 00 LUN: 5
 Library ID: 70 Slot: 5
 Vendor identification: IBM
 Product identification: ULT3580-TD4
 Product revision level: 252D
 Unit serial number: 70000075
 NAA: 70:11:22:33:ab:6:00:5
 Compression: factor 1 enabled 0

~ # tail -1 /etc/mhvtl/library_contents.70
Slot 200: CLN200L4

Let me know if you need VERBOSE logs output from mhvtl.

[Mark Harvey]

nia wrote

ANR8302E I/O error on drive DRIVE1 (/dev/IBMtape14) with
                          volume CLN200L4 (OP=READ, Error Number=5, CC=0, rc = 1,
                          KEY=02, ASC=30, ASCQ=03, SENSE=F0.00.02.00.00.00.00.58.0-
                          0.00.00.00.30.03.00.00.00.00.00.00.00.00.00.00.00.00.00.-
                          00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00-
                          .00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.0-
                          0.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.-
                          00.00.00.00.00.00.00.00.00.00.00.00.00, Description=An
                          undetermined error has occurred)

OK, decide that sense data: (ASC/ASCQ)
$ grep 3003 *.h
scsi.h:#define E_CLEANING_CART_INSTALLED        0x3003

So mhvtl / vtltape is returning a 'Not Ready / Cleaning cartridge installed' sense code to TSM..

   ------ From IBM SCSI Reference (11th edition):  ------
Sense Key 2 (Not Ready)
Table 270.
 ASC and ASQ Summary for Sense Key 2 (Not Ready)
ASC ASCQ Description
04 00 Logical Unit Not Ready, Cause Not Reportable: A tape is present in the drive, but it is in the process of being unloaded.
04 01 Logical Unit Is in Process of Becoming Ready
04 02 Initializing Command Required: A tape is present in the drive, but it is not logically loaded.
04 12 Logical Unit Not Ready, Offline
0B 01 Warning - Specified Temperature Exceeded
30 03 Cleaning Cartridge Installed
30 07 Cleaning Failure
3A 00 Medium Not Present
3E 00 Logical Unit Has Not Self-configured
   ------------------

On this surface, it all looks OK. Perhaps there is another OP code being sent to mhvtl that is not responding as TSM expects.

Any chance of bumping VERBOSE = 3 and re-trying the test ?

Cheers
Mark

[nia]

I have tried to  bump VERBOSE = 3 and re-trying the test, but for some unknown reason at this time, mhvtl started to run  really super slow, slow enough to abort this operation. Not sure what it is yet. May have something to do with my specially patched for scst kernel using VMSPLIT and NOHIGHMEM . As soon as I revert back to VERBOSE=0 then all comes back to normal.
I have even turned off scst and minimized the number of mhvtl virtual devices but still continue to run super slow.

I will continue to investigate ..

nia