On Sun, 17 Mar 2002, Thomas Hepper wrote:
> Hi, > On Fri, Mar 15, 2002 at 10:48:24AM -0500, Eric Trager wrote: > > > > I added this to the chg-scsi-solaris.conf file I use and the chg-scsi > [...] > > > > ChgExit in MapBarCode, reason MapBarCode, DB Version does not match > > > You should drop the old labelfile and rerun an amtape <conf> show I did and unfortunately, while the show ran, a labelfile was not created. I also followed John's suggestion and ran an update but with no result. However, I did reset the changer and run ./chg-scsi -label TEMP-00 which was the label of the tape in the drive at the time. I got back 0 0 0 and the labelfile was created with an entry :2:TEMP-00 So I ran a "amtape Temp slot next", which loaded the next tape, TEMP-01, and then ran the label command ./chg-scsi -label TEMP-01 and the labelfile changed, but the entry wrote over the first one: :2:TEMP-01 was all that was in the labelfile. I'm not sure what the "2" is, or what the fields are supposed to be. Just to show what the barcodes are like, here is a line from mtx: Storage Element 5:Full :VolumeTag=A00004 What do you all think? Should I just throw in the towel? I feel like I'm getting there, but the road is all over the place. - Eric PS: Here are some lines from the debug file on the "amtape Temp update" command I ran earlier: changer: got exit: 0 str: 1 20 1 0 changer: got exit: 0 str: 1 /dev/rmt/1bn changer_label: TEMP-01 for slot 1 changer: got exit: 0 str: 1 20 1 0 changer_query: changer return was 20 1 0 changer_query: searchable = 0 changer: got exit: 0 str: 2 /dev/rmt/1bn changer_label: TEMP-02 for slot 2 [etc.]
