Wrong slots / barcodes

[mir06]

Hi,

I have a strange behavior when running the status command. I got a Quantum Scalar i3 with 25 LTO-8 tapes in ascending order in slots 1-25. While the web-interface of the library reports the barcodes correctly mtx -f /dev/sg2 status sees tape 16 in slot 24, tape 24 in slot 25 and tape 25 in slot 16. If I remove tapes 24 and 25, tape 16 still in slot 24 and slot 16 is empty. If I only remove tape 25, tape 16 is in slot 24 and tape 24 in slot 16. Maybe a small table is more descriptive:

Inserted tapes	slots
16, 24, 25	25, 16, 24
16, 24	24, 16
16	24
24	16
24, 25	16, 24
25	16

All other slots are not affected at all.

Here's the output with full loading

$ sudo mtx -f /dev/sg2  status
  Storage Changer /dev/sg2:1 Drives, 25 Slots ( 0 Import/Export )
Data Transfer Element 0:Empty
      Storage Element 1:Full :VolumeTag=BAR001L8                        
      Storage Element 2:Full :VolumeTag=BAR002L8                        
      Storage Element 3:Full :VolumeTag=BAR003L8                        
      Storage Element 4:Full :VolumeTag=BAR004L8                        
      Storage Element 5:Full :VolumeTag=BAR005L8                        
      Storage Element 6:Full :VolumeTag=BAR006L8                        
      Storage Element 7:Full :VolumeTag=BAR007L8                        
      Storage Element 8:Full :VolumeTag=BAR008L8                        
      Storage Element 9:Full :VolumeTag=BAR009L8                        
      Storage Element 10:Full :VolumeTag=BAR010L8                        
      Storage Element 11:Full :VolumeTag=BAR011L8                        
      Storage Element 12:Full :VolumeTag=BAR012L8                        
      Storage Element 13:Full :VolumeTag=BAR013L8                        
      Storage Element 14:Full :VolumeTag=BAR014L8                        
      Storage Element 15:Full :VolumeTag=BAR015L8                        
      Storage Element 16:Full :VolumeTag=BAR025L8                        
      Storage Element 17:Full :VolumeTag=BAR017L8                        
      Storage Element 18:Full :VolumeTag=BAR018L8                        
      Storage Element 19:Full :VolumeTag=BAR019L8                        
      Storage Element 20:Full :VolumeTag=BAR020L8                        
      Storage Element 21:Full :VolumeTag=BAR021L8                        
      Storage Element 22:Full :VolumeTag=BAR022L8                        
      Storage Element 23:Full :VolumeTag=BAR023L8                        
      Storage Element 24:Full :VolumeTag=BAR016L8                        
      Storage Element 25:Full :VolumeTag=BAR024L8

When I activate the DEBUG_BARCODE and increase the output of the DataBuffer I can also see the mixed up allocation.

Probably this is not a problem of mtx but a bug in the scalar i3 firmware. I just wanted to report this here and maybe you already know about that.

Here my configuration:

$ sudo loaderinfo -f /dev/sg2
Product Type: Medium Changer
Vendor ID: 'QUANTUM '
Product ID: 'Scalar i3-i6    '
Revision: '277G'
Attached Changer: No
Bar Code Reader: Yes
EAAP: Yes
Number of Medium Transport Elements: 1
Number of Storage Elements: 25
Number of Import/Export Elements: 0
Number of Data Transfer Elements: 1
Transport Geometry Descriptor Page: Yes
Invertable: No
Device Configuration Page: Yes
Storage: Data Transfer, Import/Export, Storage
SCSI Media Changer (rev 2): No
Transfer Medium Transport: ->Import/Export, ->Storage
Transfer Storage: ->Data Transfer, ->Import/Export, ->Storage
Transfer Import/Export: ->Data Transfer, ->Import/Export, ->Storage
Transfer Data Transfer: ->Data Transfer, ->Import/Export, ->Storage
Exchange Medium Transport: None
Exchange Storage: None
Exchange Import/Export: None
Exchange Data Transfer: None

$ sudo tapeinfo -f /dev/sg2
Product Type: Medium Changer
Vendor ID: 'QUANTUM '
Product ID: 'Scalar i3-i6    '
Revision: '277G'
Attached Changer API: No
SerialNumber: 'QUANTUMFQL2127030_LLA   '
SCSI ID: 1
SCSI LUN: 1
Ready: yes