Hi Philipp,
You were correct setting Check Labels = no fixed the issue.  Thank you


On Wednesday, May 11, 2016 at 12:19:08 PM UTC-7, Michael Ferry wrote:
> Hi Philipp,
> Thank you for this.  You are correct I do not have ANSI/IBM labels.  I have a 
> job running now but when it finishes I will edit the storage configuration 
> file and post if this corrects the issue
> 
> On Wednesday, May 11, 2016 at 12:22:21 AM UTC-7, philipp.storz wrote:
> > Hello,
> > 
> > I doubt that you have ANSI/IBM labels, do you?
> > 
> > Then please set  "Check Labels" to no.
> > 
> > 
> > On 11.05.2016 03:30, Michael Ferry wrote:
> > > Hello, I have recently installed bareos on a centos 7.1 system using a 
> > > Quantum scalar i40 tape
> > > library with a IBM ultrium LTO-6 tape drive.  So far things are going 
> > > well although I am
> > > encountering an error that shows up when I change tapes in the tape 
> > > drive.  The error shows up in
> > > the bareos log as:
> > > 
> > > 2016-05-10 18:07:41       burr-sd JobId 250: Error:
> > > 
> > > and when I run dmesg I see this:
> > > 
> > > st 10:2:0:0: st0: Failed to read 201 byte block with 80 byte transfer.
> > > 
> > > From reading the bareos manual I suspect there is an issue getting the 
> > > correct block size for
> > > reading the bareos label.  I notice after labeling blank tapes using the 
> > > bconsole label barcode
> > > command the volumes in one of my pools have volume bytes listed as 201 
> > > and another as 199  When
> > > these volumes are loaded I will see an error like that above but the with 
> > > byte block size
> > > matching that of the pool (so when I have a volume originally containing 
> > > 199 bytes the message
> > > will be:
> > > 
> > > st 10:2:0:0: st0: Failed to read 199 byte block with 80 byte transfer.
> > > 
> > > After this error the backup proceeds normally and I will get a job 
> > > completed with warnings
> > > notification.  I can restore files without issue.  The error is mostly 
> > > annoying because all of my
> > > jobs that require tapes to be changed show up as completing with a 
> > > warning.  I did change the
> > > maximum block size of my device in the storage director configuration 
> > > file as follows:
> > > 
> > > Device { Name = "ULTRIUM-HH6" DeviceType = tape
> > > 
> > > # default:0, only required if the autoloader have multiple drives. 
> > > DriveIndex = 0
> > > 
> > > # if only one drive is available, this is normally /dev/nst0. # However, 
> > > it is advised to access
> > > it via id (/dev/tape/by-id/...). #ArchiveDevice = /dev/nst0 ArchiveDevice 
> > > =
> > > /dev/tape/by-id/scsi-3500308c38ea67000-nst
> > > 
> > > 
> > > # arbitrary string that descripes the the storage media. # Bareos uses 
> > > this to determine, which
> > > device can be handle what media. MediaType = LTO6
> > > 
> > > #LabelMedia set to no seems to be what bareos expects for tape drives 
> > > LabelMedia = no
> > > 
> > > # enable "Check Labels" if tapes with ANSI/IBM labels # should be 
> > > preserved Check Labels = yes
> > > 
> > > AutomaticMount = yes                    # default: no AlwaysOpen = yes 
> > > RemovableMedia = yes 
> > > RandomAccess = no AutoChanger = yes                       # default: no 
> > > MaximumFileSize = 20GB
> > > # default: 1000000000 (1GB)
> > > 
> > > MaximumBlockSize = 1048576 }
> > > 
> > > Autochanger { Name = "QUANTUM_Scalar_i40" # adapt this, to match your 
> > > storage loader #Changer
> > > Device = /dev/tape/by-id/scsi-1TANDBERGStorageLoader_AA45JC001732 Changer 
> > > Device =
> > > /dev/tape/by-id/scsi-1QUANTUM_D0H0113301_LLA
> > > 
> > > # an Autochanger can contain multiple drive devices Device = ULTRIUM-HH6 
> > > #Device = tapedrive-1
> > > 
> > > Changer Command = "/usr/lib/bareos/scripts/mtx-changer %c %o %S %a %d" }
> > > 
> > > The pool definitions in my director configuration file (note the full 
> > > pool is associated with an
> > > initial volume size of 201 bytes and the incremental pool of 199 bytes):
> > > 
> > > # # Full Tape Pool definition # Pool { Name = Full_Tape Pool Type = 
> > > Backup Recycle = yes
> > >  Recycle Pool = Scratch AutoPrune = yes                     # Prune 
> > > expired volumes Storage =
> > > "ULTRIUM-HH6" Volume Retention = 365 days         # Maximum Volumes = 100 
> > >               # Limit
> > > number of Volumes in Pool }
> > > 
> > > 
> > > # # Incremental Pool definition # Pool { Name = Incremental_Tape Pool 
> > > Type = Backup Recycle = yes
> > >  Recycle Pool = Scratch AutoPrune = yes                     # Prune 
> > > expired volumes Storage =
> > > "ULTRIUM-HH6" Volume Retention = 30 days Maximum Volumes = 100            
> > >    # Limit number of
> > > Volumes in Pool }
> > > 
> > > Any help you could give me would be very much appreciated.  I am new to 
> > > bareos but I am very
> > > impressed with its capability.  Thank you, Michael
> > > 
> > 
> > 
> > -- 
> > Mit freundlichen Grüßen
> > 
> >  Philipp Storz                             [email protected]
> >  Bareos GmbH & Co. KG                      Phone: +49 221 63 06 93-92
> >  http://www.bareos.com                     Fax:   +49 221 63 06 93-10
> > 
> >  Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
> >  Geschäftsführer: Stephan Dühr, M. Außendorf,
> >  J. Steffens, P. Storz, M. v. Wieringen

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to