Hello John,
The delay was exactly the problem--Neither mtx nor the chg-zd-mtx script
allowed for a delay between unloading one tape and loading the next one,
and the changer did not like this. I editted the chg-zd-mtx script and
put in a "sleep 30" command (may increase that value to be on the safe
side) and that seems to have fixed the problem.
As for the reset, I have an Exabyte 10h and Exabyte Mammoth on the same
SCSI bus--The 10h and Mammoth both stopped what they were doing and did
their usual initialization bit (which even choked a restore that I was
running on the Mammoth at the time). My guess is that mtx decided that
the changer wasn't responding so it reset the bus.
"John R. Jackson" wrote:
> I know zip about mtx, but the basic driver code for my robot (akin to
> mtx) did not have sufficient timeouts to allow for "long" movements.
> Cranking them up (from 30 seconds to 90 or so, as I recall) made my life
> a **whole** lot better :-).
>
> When watching the box, how long does it take to do a complete movement,
> i.e. unload one tape, put it away, put the next one in the drive and
> wait for it to go ready? Are there tweakable timeouts in mtx, either
> the source or command line?
--
"Jonathan F. Dill" ([EMAIL PROTECTED])
CARB Systems and Network Administrator
Home Page: http://www.umbi.umd.edu/~dill
