On 10/06/2014 02:47 PM, Mike Driscoll wrote:
Jean-Louis,
$ amtape Weekly1-library1 inventory
…
slot 16: unknown state barcode CA0017
And what's the label on that tape, it it loaded in /dev/st0: mt -f
/dev/nst0 rewind; dd if=/dev/nst0 bs=32k count=1
[amandabackup@ca-server10 ~]$ amlabel Weekly1
Jean-Louis,
$ amtape Weekly1-library1 inventory
…
slot 16: unknown state barcode CA0017
[amandabackup@ca-server10 ~]$ amlabel Weekly1-library1 slot 16
Reading label...
Slot 16, label 'Weekly1-library1-CA0014', mismatch barcode between changer
'CA0017' and tapelist file 'CA0014'
I confirmed in t
On 10/02/2014 09:40 PM, Mike Driscoll wrote:
Hi Jean-Louis. I am using version 3.3.6. I am confident that tape-device is
correct insofar as I can complete multiple, successful dumps before the
mismatches begin.
amtape verify looks good…
$ amtape Weekly1-library1 verify
GOOD : Drive 0 is dev
After I have confidence in the configuration
>> and some testing, the first few actual, scheduled dumps run fine. But
>> around the 4th or 5th regularly scheduled dump, I consistently get errors
>> about barcode mismatches with tape labels.
>>
>> I label t
library for the first time, a StorageTek SL150 with two
LTO6 drives. After I have confidence in the configuration and some testing,
the first few actual, scheduled dumps run fine. But around the 4th or 5th
regularly scheduled dump, I consistently get errors about barcode mismatches
with tape
the 4th or 5th
regularly scheduled dump, I consistently get errors about barcode mismatches
with tape labels.
I label tapes using commands like this:
amlabel -f --barcode CA0014 Weekly1-library1 Weekly1-library1-CA0014
First, is there documentation to define specific definitions for LTO6 and
