Issues with IBM Labels

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Issues with IBM Labels

Jim Richardson
Hello,

I must be missing something stupid.  I am using IBM barcode labels on LTO7 tapes.  Bacula labeled my media, but I am unable to start backup job due to error Fatal error: ansi_label.c:296 ANSI Volume label name "000009L7" longer than 6 chars.

BConsole Steps:
*label barcodes
*- snip -*
*update slots
Device "ULT3580" has 8 slots.
Catalog record for Volume "000009L7" is up to date.
Catalog record for Volume "000001L7" is up to date.
Catalog record for Volume "000008L7" is up to date.
Catalog record for Volume "000003L7" is up to date.
Catalog record for Volume "000006L7" is up to date.
Catalog record for Volume "000005L7" is up to date.
Catalog record for Volume "CLN002L1" is up to date.
Catalog record for Volume "000007L7" is up to date.

17-Apr 20:16 bacula-dir JobId 18: Start Backup JobId 18, Job=Backup_TestData.2017-04-17_20.16.03_19
17-Apr 20:16 bacula-dir JobId 18: Using Device "ULT3580" to write.
17-Apr 20:16 bacula-sd JobId 18: 3307 Issuing autochanger "unload slot 3, drive 0" command for vol 000009L7.
17-Apr 20:16 bacula-sd JobId 18: 3304 Issuing autochanger "load slot 1, drive 0" command for vol 000009L7.
17-Apr 20:17 bacula-sd JobId 18: 3305 Autochanger "load slot 1, drive 0", status is OK for vol 000009L7.
17-Apr 20:17 bacula-sd JobId 18: Error: 17-Apr 20:17 bacula-sd JobId 18: Fatal error: ansi_label.c:296 ANSI Volume label name "000009L7" longer than 6 chars.
17-Apr 20:17 bacula-fd JobId 18: Fatal error: job.c:2484 Bad response from SD to Append Data command. Wanted 3000 OK data
, got len=114 msg="3903 Error append data: ansi_label.c:85 Read error on device /dev/nst0 in ANSI label. ERR=Cannot allocate memory  "
17-Apr 20:17 bacula-sd JobId 18: Marking Volume "000009L7" in Error in Catalog.
17-Apr 20:17 bacula-sd JobId 18: Fatal error: Job 18 canceled.


#-- /etc/bacula/bacula-sd.conf
Device {
  Name                  = ULT3580
  Description           = "IBM ULT3580-HH7"
  Media Type            = LTO-7
  Archive Device        = /dev/nst0
  Label Type            = IBM;
  AutomaticMount        = yes;               # when device opened, read it
  AlwaysOpen            = yes;
  RemovableMedia        = yes;
  RandomAccess          = no;
  AutoChanger           = yes;
  Changer Device        = /dev/sg6
  Drive Index           = 0
  Spool Directory       = /backup/bacula/spool
  Changer Command       = "/usr/libexec/bacula/mtx-changer %c %o %S %a %d"
  # Enable the Alert command only if you have the mtx package loaded
  Alert Command         = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
}

#-- /etc/bacula/bacula-dir.conf
Pool {
  Name = Daily_Tapes
  Pool Type = Backup
  Cleaning Prefix = "CLN"
  Recycle = yes
  AutoPrune = yes
  Volume Retention = 6 days
  Recycle Oldest Volume = yes
  Label Type = IBM
}


Thanks!

Jim Richardson

CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this email from your system. Thank you.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bacula-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Issues with IBM Labels

Kern Sibbald
Hello,

I suspect that you have mistaken using IBM barcode labels (all LTO
labels are the same format), and ANSI/IBM tape labels.

Barcode labels are physical stickers that are put on a cartridge so that
the barcode scanner in your autochanger can identify the tape name.

Within Bacula itself there exists a function to turn on ANSI/IBM tape
labeling which is something very special that puts generic tape labels
on the tape itself (it is a special label record). Unless you really
know what you are doing and are sharing tapes among several different
backup programs, you should not be using ANSI tape labeling.

Recommendations:

1. Turn off ANSI/IBM tape labeling in your bacula-sd.conf file. If you
never added it, then very likely you have a broken Bacula binary.

2. Delete all the catalog Volumes that you list below.

3. Mount each tape one at a time, and with mt rewind the tape and write
two EOF marks.

4. Redo the label barcodes, and update slots.

5. All should be normal.

Note: ANSI labels are limited to 6 characters.  Theoretically the Bacula
code works, but I don't think anyone has used it for over 10 years,
which means there is a high probability that if you really want to use
it you will run into problems.

Best regards,

Kern





On 04/18/2017 04:00 AM, Jim Richardson wrote:

> Hello,
>
> I must be missing something stupid.  I am using IBM barcode labels on LTO7 tapes.  Bacula labeled my media, but I am unable to start backup job due to error Fatal error: ansi_label.c:296 ANSI Volume label name "000009L7" longer than 6 chars.
>
> BConsole Steps:
> *label barcodes
> *- snip -*
> *update slots
> Device "ULT3580" has 8 slots.
> Catalog record for Volume "000009L7" is up to date.
> Catalog record for Volume "000001L7" is up to date.
> Catalog record for Volume "000008L7" is up to date.
> Catalog record for Volume "000003L7" is up to date.
> Catalog record for Volume "000006L7" is up to date.
> Catalog record for Volume "000005L7" is up to date.
> Catalog record for Volume "CLN002L1" is up to date.
> Catalog record for Volume "000007L7" is up to date.
>
> 17-Apr 20:16 bacula-dir JobId 18: Start Backup JobId 18, Job=Backup_TestData.2017-04-17_20.16.03_19
> 17-Apr 20:16 bacula-dir JobId 18: Using Device "ULT3580" to write.
> 17-Apr 20:16 bacula-sd JobId 18: 3307 Issuing autochanger "unload slot 3, drive 0" command for vol 000009L7.
> 17-Apr 20:16 bacula-sd JobId 18: 3304 Issuing autochanger "load slot 1, drive 0" command for vol 000009L7.
> 17-Apr 20:17 bacula-sd JobId 18: 3305 Autochanger "load slot 1, drive 0", status is OK for vol 000009L7.
> 17-Apr 20:17 bacula-sd JobId 18: Error: 17-Apr 20:17 bacula-sd JobId 18: Fatal error: ansi_label.c:296 ANSI Volume label name "000009L7" longer than 6 chars.
> 17-Apr 20:17 bacula-fd JobId 18: Fatal error: job.c:2484 Bad response from SD to Append Data command. Wanted 3000 OK data
> , got len=114 msg="3903 Error append data: ansi_label.c:85 Read error on device /dev/nst0 in ANSI label. ERR=Cannot allocate memory  "
> 17-Apr 20:17 bacula-sd JobId 18: Marking Volume "000009L7" in Error in Catalog.
> 17-Apr 20:17 bacula-sd JobId 18: Fatal error: Job 18 canceled.
>
>
> #-- /etc/bacula/bacula-sd.conf
> Device {
>    Name                  = ULT3580
>    Description           = "IBM ULT3580-HH7"
>    Media Type            = LTO-7
>    Archive Device        = /dev/nst0
>    Label Type            = IBM;
>    AutomaticMount        = yes;               # when device opened, read it
>    AlwaysOpen            = yes;
>    RemovableMedia        = yes;
>    RandomAccess          = no;
>    AutoChanger           = yes;
>    Changer Device        = /dev/sg6
>    Drive Index           = 0
>    Spool Directory       = /backup/bacula/spool
>    Changer Command       = "/usr/libexec/bacula/mtx-changer %c %o %S %a %d"
>    # Enable the Alert command only if you have the mtx package loaded
>    Alert Command         = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
> }
>
> #-- /etc/bacula/bacula-dir.conf
> Pool {
>    Name = Daily_Tapes
>    Pool Type = Backup
>    Cleaning Prefix = "CLN"
>    Recycle = yes
>    AutoPrune = yes
>    Volume Retention = 6 days
>    Recycle Oldest Volume = yes
>    Label Type = IBM
> }
>
>
> Thanks!
>
> Jim Richardson
>
> CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this email from your system. Thank you.
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Bacula-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bacula-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Issues with IBM Labels

Ralf Brinkmann
In reply to this post by Jim Richardson
Am 18.04.2017 um 04:00 schrieb Jim Richardson:
> I must be missing something stupid.  I am using IBM barcode labels on
> LTO7 tapes.  Bacula labeled my media, but I am unable to start backup
> job due to error Fatal error: ansi_label.c:296 ANSI Volume label name
> "000009L7" longer than 6 chars.

Just looked into our old DELL PowerVault web interface. Years ago for
the same lable length I configured:

> Configure Library
>   General
>     Barcode Label Length Reported To Host = 8

I included the two trailing digits for the tape type into the label length.

--
Ralf Brinkmann

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bacula-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Issues with IBM Labels

Kern Sibbald
I already wrote this previously: the error message produced by Bacula
indicates that the user has enabled ANSI volume labels. This is unusual
and generally not needed unless you have multiple different backup/other
programs using the tapes.  In any case, if you explicitly enable this
ANSI tape label option in Bacula (turned off by default), you are
limited to 6 characters in the tape name.   Without the ANSI tape label
option in the bacula-sd.conf file, your tape labels may be up to 127
characters in length.

As I previously wrote, I think that the user is confusing barcodes and
reading barcodes with the ANSI tape labels feature in Bacula.

Best regards,

Kern



On 05/05/2017 10:46 AM, Ralf Brinkmann wrote:

> Am 18.04.2017 um 04:00 schrieb Jim Richardson:
>> I must be missing something stupid.  I am using IBM barcode labels on
>> LTO7 tapes.  Bacula labeled my media, but I am unable to start backup
>> job due to error Fatal error: ansi_label.c:296 ANSI Volume label name
>> "000009L7" longer than 6 chars.
> Just looked into our old DELL PowerVault web interface. Years ago for
> the same lable length I configured:
>
>> Configure Library
>>    General
>>      Barcode Label Length Reported To Host = 8
> I included the two trailing digits for the tape type into the label length.
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bacula-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Issues with IBM Labels

Jim Richardson
Kern, thanks for the the reiterate. I solved this problem in April with your first response. I removed references to IBM labels and after a delete and readd everything is working properly.

Sent from my Android phone using TouchDown (www.symantec.com)

-----Original Message-----
From: Kern Sibbald [[hidden email]]
Received: Friday, 05 May 2017, 3:59AM
To: Ralf Brinkmann [[hidden email]]; Jim Richardson [[hidden email]]; [hidden email] [[hidden email]]
Subject: Re: [Bacula-users] Issues with IBM Labels

I already wrote this previously: the error message produced by Bacula
indicates that the user has enabled ANSI volume labels. This is unusual
and generally not needed unless you have multiple different backup/other
programs using the tapes.  In any case, if you explicitly enable this
ANSI tape label option in Bacula (turned off by default), you are
limited to 6 characters in the tape name.   Without the ANSI tape label
option in the bacula-sd.conf file, your tape labels may be up to 127
characters in length.

As I previously wrote, I think that the user is confusing barcodes and
reading barcodes with the ANSI tape labels feature in Bacula.

Best regards,

Kern



On 05/05/2017 10:46 AM, Ralf Brinkmann wrote:
> Am 18.04.2017 um 04:00 schrieb Jim Richardson:
>> I must be missing something stupid.  I am using IBM barcode labels on
>> LTO7 tapes.  Bacula labeled my media, but I am unable to start backup
>> job due to error Fatal error: ansi_label.c:296 ANSI Volume label name
>> "000009L7" longer than 6 chars.
> Just looked into our old DELL PowerVault web interface. Years ago for
> the same lable length I configured:
>
>> Configure Library
>>    General
>>      Barcode Label Length Reported To Host = 8
> I included the two trailing digits for the tape type into the label length.
>

CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this email from your system. Thank you.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bacula-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Issues with IBM Labels

Kern Sibbald

OK, thanks for the feedback.   My response was mostly for Ralf, which is why I referred to "the user" i.e. you in my responses, but I wasn't 100% sure.  It is good to know that the problem is resolved.

Best regards,

Kern


On 05/05/2017 06:22 PM, Jim Richardson wrote:
Kern, thanks for the the reiterate. I solved this problem in April with your first response. I removed references to IBM labels and after a delete and readd everything is working properly.

Sent from my Android phone using TouchDown (www.symantec.com)

-----Original Message-----
From: Kern Sibbald [[hidden email]]
Received: Friday, 05 May 2017, 3:59AM
To: Ralf Brinkmann [[hidden email]]; Jim Richardson [[hidden email]]; [hidden email] [[hidden email]]
Subject: Re: [Bacula-users] Issues with IBM Labels

I already wrote this previously: the error message produced by Bacula
indicates that the user has enabled ANSI volume labels. This is unusual
and generally not needed unless you have multiple different backup/other
programs using the tapes.  In any case, if you explicitly enable this
ANSI tape label option in Bacula (turned off by default), you are
limited to 6 characters in the tape name.   Without the ANSI tape label
option in the bacula-sd.conf file, your tape labels may be up to 127
characters in length.

As I previously wrote, I think that the user is confusing barcodes and
reading barcodes with the ANSI tape labels feature in Bacula.

Best regards,

Kern



On 05/05/2017 10:46 AM, Ralf Brinkmann wrote:
> Am 18.04.2017 um 04:00 schrieb Jim Richardson:
>> I must be missing something stupid.  I am using IBM barcode labels on
>> LTO7 tapes.  Bacula labeled my media, but I am unable to start backup
>> job due to error Fatal error: ansi_label.c:296 ANSI Volume label name
>> "000009L7" longer than 6 chars.
> Just looked into our old DELL PowerVault web interface. Years ago for
> the same lable length I configured:
>
>> Configure Library
>>    General
>>      Barcode Label Length Reported To Host = 8
> I included the two trailing digits for the tape type into the label length.
>

CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this email from your system. Thank you.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bacula-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Issues with IBM Labels

Dan Langille
In reply to this post by Kern Sibbald
> On Apr 18, 2017, at 4:45 AM, Kern Sibbald <[hidden email]> wrote:
>
> 3. Mount each tape one at a time, and with mt rewind the tape and write
> two EOF marks.

Why two EOF marks?

--
Dan Langille - BSDCan / PGCon
[hidden email]


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bacula-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Issues with IBM Labels

Kern Sibbald
Because on older tape drives (DDS, DLT, ...) one EOF means End of File;
two consecutive EOF marks with nothing between means End of Data.

On all modern drives only one EOF is necessary.


On 05/06/2017 04:49 PM, Dan Langille wrote:
>> On Apr 18, 2017, at 4:45 AM, Kern Sibbald <[hidden email]> wrote:
>>
>> 3. Mount each tape one at a time, and with mt rewind the tape and write
>> two EOF marks.
> Why two EOF marks?
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bacula-users
Loading...