Re: [Mtx-general] Mode Sense Hanging

[Eric L. G. <er...@ba...>]

On Tuesday 22 July 2003 06:54 am, Charles M. Richmond wrote:
> Using Solaris 2.8 with an Overland LibraryPro changer. I have a hang
> on all commands except 'inquiry'. The changer goes into a busy state
> as the hang is in the driver.
>
> I have verified this with each version of mtx from 1.2.15 to 1.2.18rel.
> I am told that mtx worked before, and that patches to Solaris might
> have been the gating factor to the problem.
>
> # mt -f /dev/rmt/0 offline
> /dev/rmt/0: no tape loaded or drive offline
> # mt -f /dev/rmt/1 offline
> /dev/rmt/1: no tape loaded or drive offline
> # mt -f /dev/changer offline
> /dev/changer offline 1 failed: Inappropriate ioctl for device
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I assume you're using the 'sgen' driver? If so, the above ioctl attempt may 
have put the 'sgen' driver into an uncertain state (I have *not* been 
impressed by the stability of Solaris's drivers when it comes to tape and 
loaders). If you're using another driver, there may be more problems. 


> # ./mtx inquiry
> ------CDB--------
> 0000:12 00 00 00 38 00
> --------input data-----------
> 0000:08 80 4a 02 33 00 00 30 4f 56 45 52 4c 41 4e 44 4c 49 42 52 41 52 59
> 50 52 0019:4f 20 20 20 20 20 20 30 34 32 30 31 39 2d 41 70 72 2d 30 32 00
> 00 00 00 00 0032:00 00 15 01 02 01
> Product Type: Medium Changer
> Vendor ID: 'OVERLAND'
> Product ID: 'LIBRARYPRO      '
> Revision: '0420'

Well, you're up to date on your firmware at least. 

> Attached Changer: No
>
> (Note: the 12 is the inquiry command, the 38 is the byte count and the
>  hex data corresponds to the return)
>
> # ./mtx load
> ------CDB--------
> 0000:12 00 00 00 38 00
> --------input data-----------
> 0000:08 80 4a 02 33 00 00 30 4f 56 45 52 4c 41 4e 44 4c 49 42 52 41 52 59
> 50 52 0019:4f 20 20 20 20 20 20 30 34 32 30 31 39 2d 41 70 72 2d 30 32 00
> 00 00 00 00 0032:00 00 15 01 02 01
> ------CDB--------
> 0000:1a 00 1d 00 88 00

It's requesting the Element Address Assigment Page. This tells how many of 
each type of element are mapped into the loader's address space, and where 
they start, element address wise. mtx uses that information to allocate its 
internal structures using malloc() and in order to know how many elements to 
request from READ_ELEMENT_STATUS for each type of element. 

I have no idea why things are hanging at this point. The Overland should 
support the EAAP, Overland generally puts out good gear that's pretty 
SMC-compliant (I'm trying to get the manual from their website to make sure, 
but I'm 99% positive there's no problem there).  Can you find out what driver 
you're using for /dev/changer?

-- 
Eric Lee Green  mailto:er...@ba...
Unix/Linux/Storage Software Engineer needs job -- 
see http://badtux.org for resume