Would also verify your drive.   I've had issues with LTO drives that just flake 
out over time and required replacement from the vendors in the past.  Most 
vendors supply a test utility.

As for the block size limit increase, that's not correct.   Even though it was 
stated in the change logs that it's been upped to 20,000,000 bytes, that is 
incorrect.   The code in dev.c is still locked to 4096000 bytes (1000 4K pages) 
this is hard-coded, which you can change & re-compile.

Steve



>-----Original Message-----
>On 09/03/12 11:51, Phil Stracchino wrote:
>> All of a sudden, my Bacula-5.2.10 storage daemon keeps crashing with the
>> following error reported:
>
>Preliminary analysis at this point appears to indicate that it is a
>REALLY bad idea on an LTO drive to have bacula-sd's configured max block
>size not an exact multiple of LTO's native 1024-byte block unit.
>
>So, someone recently observed you could set max block size up to 2000000
>on an LTO4 drive, with 2000000 being a Bacula internal limit.  Well, and
>so you can; but don't use 2000000.  Use a multiple of 1024.  I've reset
>mine to 1024000 and I'm getting a sustained 72.5MB/s write to a HP
>external LTO4 on an LSI Logic Falcon series SAS-2 controller.  (SAS2008,
>specifically.)




------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users