Amanda-Users

HELLO, I have trouble with chg-scsi: wrong emubarcode number

2003-07-25 12:34:23
Subject: HELLO, I have trouble with chg-scsi: wrong emubarcode number
From: Ashwin Bijur <abijur AT craft-tech DOT com>
To: amanda-users <amanda-users AT amanda DOT org>
Date: Fri, 25 Jul 2003 12:32:50 -0400

I am experiencing a problem with chg-scsi.  Whenever I execute "chg-scsi -inventory", I get back the following response:
 BarCode == 1 and emubarcode == 1

Our tape-changer is equipped with a bar code reader.  I have set "havebarcode 1", "emubarcode 0" in the chg-scsi.conf file.  But chg-scsi doesn't seem to pickup this information.  When I ran "strings -a /usr/local/etc/libexec/chg-scsi | grep emubarcode", I got the following output:

emubarcode
emubarcode       1   # If you drive has no barcode reader this will try
BarCode == 1 and emubarcode == 1
emubarcode


So it seems that emubarcode is hardcoded as 1 in the binary file.  Is there any way to fix this or force chg-scsi to read the value for emubarcode from the chg-scsi.conf file?

When I run "chg-scsi -genconf", I get the following information:
Count 1
Count 2
Count 3
Count 4
# Please replace every ??? with the correct parameter. It is not possible
# to guess everything :-)
# If the option is not needed, cleanmax for example if you have no cleaning
# tape remove the line.
#
number_configs   1   # Number of configs, you can have more than 1 config
                     # if you have for example more than one drive, or you
                     # to split your lib to use different dump levels
                     #
emubarcode       1   # If you drive has no barcode reader this will try
                     # keep an inventory of your tapes to find them faster
                     #
havebarcode      0   # Set this to 1 if you have an library with an installed
                     # barcode reader
                     #
debuglevel       0:0 # For debuging, see the docs /docs/TAPE-CHANGER
                     #
eject            ??? # set this to 1 if your drive needs an eject before move
                     #
sleep            ??? # How long to wait after an eject command before moving
                     # the tape
                     #
changerdev   /dev/sg0 # This is the device to communicate with the robot
                     #
                     # Here now comes the config for the first tape
config             0 # This value is the one which is used in the amanda
                     # config file to tell the chg-scsi programm which tape
                     # and which slots to use
                     #
cleancart        ??? # The slot where the cleaning tape is located
                     # remove it if you have no cleaning tape
                     #
drivenum           0 # Which tape drive to use if there are more than one drive
                     #
dev              ??? # Which is the raw device to read/write data from the tape
                     # It is important to use the non rewinding tape, like
                     # /dev/nrst0 on linux, /dev/nrsa0 on BSD ....
                     #
scsitapedev   /dev/sg1 # This is the device to communicate with the tape
                     # to get some device stats, not so importatn, and
                     # if you run in problems delete it complete
                     #
startuse          0  # Which is the first slot to use
                     #
enduse            21  # Which is the last slot to use
                     # decrement this value by 1 if you have an
                     # cleaning tape in the last slot
                     #
statfile /var/lib/amanda/tape0-slot #
cleanfile /var/lib/amanda/tape0-clean #
usagecount /var/lib/amanda/tape0-totaltime #
tapestatus /var/lib/amanda/tape0-tapestatus #
labelfile /var/lib/amanda/labelfile #




Here are the details about our system:

OS: Redhat 9.0
Amanda version: 2.4.4
Tapetype: AME_225_SmartClean (Exabyte)

Processor: dual processors Intel Pentium III 450MHz.

Your assistance will be much appreciated.

Thanks,
Ashwin Bijur.

<Prev in Thread] Current Thread [Next in Thread>