>From: Martin Simmons
>> On Fri, 13 Apr 2012 09:13:31 +0000, Steve Costaras said:
>> It's falling through down to 64512 when I have anything set larger than 
>> 2097152 for maximum block size.
>
>Yes, but it looks like this fails to report the error on startup:
>
>   if (dev->max_block_size > 4096000) {
>      Jmsg3(jcr, M_ERROR, 0, _("Block size %u on device %s is too large, using 
> default %u\n"),
>         dev->max_block_size, dev->print_name(), DEFAULT_BLOCK_SIZE);
>      dev->max_block_size = 0;
>   }


Good catch!  It should really notify (would have saved some time in trouble- 
shooting

Also is there a reason why this is hard coded in dev.c to 4096000 opposed to 
using  MAX_BLOCK_LENGTH ?    Which was upped to 20000000 (so there's only one 
define to change).



>
>> WITH 2097152 as maximum block size I'm getting:
>> 
>> ---
>> Device status:
>> Device "FileStorage" (/tmp) is not open.
>> Device "LTO4" (/dev/nst0) is mounted with:
>>     Volume:      FA0060
>>     Pool:        BackupSetFA
>>     Media type:  LTO4
>>     Total Bytes=223,244,193,792 Blocks=106,452 Bytes/block=2,097,134
>>     Positioned at File=20 Block=4,070
>> ====
>> --
>> 
>> which is smaller than what I'm setting by ?18 bytes?  I don't get that at 
>> all.
>
>It is a maximum, so you can't expect every block to be that size.

Figured that but what would cause it to decrease (in this case I'm de-spooling 
an 800+ GB file to an LTO4 tape that has a lot of length still on it).   So 
trying to figure out as to why it would be trimmed down?






------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users