exact same problem:
[amanda@bserver fontenot]$ mtx --version
mtx version 1.2.13
[amanda@bserver fontenot]$ mtx status
Storage Changer /dev/changer:2 Drives, 11 Slots ( 0 Import/Export )
Data Transfer Element 0:Empty
Data Transfer Element 1:Empty
Storage Element 1:Full
Storage Element 2:Full :VolumeTag=
Storage Element 3:Full
Storage Element 4:Full
Storage Element 5:Full :VolumeTag=
Storage Element 6:Full
Storage Element 7:Full
Storage Element 8:Full
Storage Element 9:Full
Storage Element 10:Full :VolumeTag=
Storage Element 11:Full
This is an ExaByte EXB-210 library with one 8mm tape drive,
no barcode reader.
The chg-scsi in 2.4.2p2 and 2.5.0 cvs does not work right with
this changer - after loading 10th tape won't do anything else
(yes, I have gravity set to 0) -
so I switched to mtx which controls the changer great.
Unfortunately, of the three(!) chg-mtx type scripts now at my
disposal - two come with amanda, one with mtx - NONE of them
work right.
Between chg-scsi not working and this problem, amanda is taking me
a lot longer to get going than it should.
I also lost a day because the cvs version of amlabel does not
report errors like the 2.4.2p2 version does - it did not give me
the sense errors so I had no way of knowing that it was failing
due to bad tapes. Once I reverted to 2.4.2p2 that problem became
obvious.
Dwayne
., "John R. Jackson" <[EMAIL PROTECTED]> wrote:
> >Still I have problems with amanda 2.4.2p2 and my changer. I got the
> >error "amcheck-server: could not get changer info: badly formed
result
> >from changer: "/usr/local/libexec/chg-zd-mtx: [: -eq: unary
operator
> >expected"
>
> What version of mtx are you using? What does "mtx -f /dev/sga
status"
> have to say (in particular, the "Data Transfer Element" lines)?
>
> >Sandra
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
