sorry did not see this mail until now
And sorry about the missleading LTO5 in my first toppic.
We use LTO6 on the bareos Server.

i have configured the max blocksize in the device section of my tape
drives. At the moment i have switched back to the default values and
moved all written tapes to a new pool with the 1M blocksize.

HPs documentation about the LTO6 drives says, that you should not go
after 256 KB blocksize
(https://docs.oracle.com/cd/E38452_01/en/LTO6_Vol5_E1/LTO6_Vol5_E1.pdf).
Saddly my Drives are IBM and I can not find writings from IBM about this.

Maybe there is something going on at the hardware on some drives and a
btape fill will rise errors (sometimes) where btape test does not.

I will schedule a btape fill for tomorrow morning with the big blocksize
to test this.


On 28.04.2015 09:34, Philipp Storz wrote:
> Hello,
> 
> we are using 1M blocksize ourselves with LTO5 and LTO6  and we do not
> have those problems.
> 
> How did you configure the blocksizes? (Device or pool?)
> 
> Best regards,
> 
> Philipp
> 
> Am 24.04.2015 um 14:44 schrieb Bernd Wollny:
>> Am Donnerstag, 23. April 2015 09:53:01 UTC+2 schrieb Rene Arnhold:
>>> Hi List
>>>
>>>
>>> On the second drive I sometimes see "device or ressource busy" errors on
>>> the drive wich lead bareos to load another tape and in the past it
>>> stopped backup jobs with "intervention needed" errors.
>>>
>>
>> Hi,
>> i am just setting up a Quantum Scalar i80 with LTO6. I have changed my
>> block size and I get the same errors.
>>
>> I will try to switch back to the default size .... and look if the
>> errors went ago.
>>
>>
>>
> 
> 


__________ Information from ESET Mail Security, version of virus signature 
database 11551 (20150429) __________

The message was checked by ESET Mail Security.
http://www.eset.com


-- 
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