Amanda 2.5.0 upgrade weirdness

Hi,

The upgrade to 2.5.0 three days ago has resulted in some odd problems,including failures to write to tape.


The Exabyte VXA-2 robot reports...

/etc/amanda/DailySet1# mtx -f /dev/sg0 status
 Storage Changer /dev/sg0:1 Drives, 10 Slots ( 0 Import/Export )

Data Transfer Element 0:Full (Storage Element 3 Loaded):VolumeTag =B0000003

     Storage Element 1:Full :VolumeTag=B0000001
     Storage Element 2:Full :VolumeTag=B0000002
     Storage Element 3:Empty:VolumeTag=
     Storage Element 4:Full :VolumeTag=B0000004
     Storage Element 5:Full :VolumeTag=B0000005
     Storage Element 6:Full :VolumeTag=B0000006
     Storage Element 7:Full :VolumeTag=B0000007
     Storage Element 8:Full :VolumeTag=B0000008
     Storage Element 9:Full :VolumeTag=B0000009
     Storage Element 10:Full :VolumeTag=B0000010

and
/etc/amanda/DailySet1# mt-st -f /dev/nst0 status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 0 bytes. Density code 0x81 (DLT 15GB compressed).
Soft error count since last status=0
General status bits on (41010000):
BOT ONLINE IM_REP_EN

Yet amtape reports...

$ amtape DailySet1 current
changer: got exit: 0 str: 3 10 1
changer_query: changer return was 10 1
changer_query: searchable = 0
amtape: scanning current slot in tape-changer rack:
changer: got exit: 0 str: 3 /dev/nst0
slot 3: not an amanda tape (Invalid argument)

changer-barcodes is empty. amlabel returns errors similar to amtapeabove. The tapes are not write-protected.

Any ideas?



--
Brad Willson, Sr. Computer Specialist
UW GeneTests, UW Box: 358735
EM: bwil150n AT u.washington DOT edu
W: 206.221.4674, C: 425.891.2732
http://www.genetests.org