On Fri, 23 May 2008 14:58:02 -0400
Alex Chekholko <chekh AT pcbi.upenn DOT edu> wrote:

> btape: btape.c:831 Wrote 1000 blocks of 1048476 bytes.
> btape: btape.c:505 Wrote 1 EOF to "Drive-0" (/dev/nst2)

This number is surprising to me because I set
Maximum block size = 1048576
What happens to the 100 bytes?

> btape: btape.c:847 Wrote 1000 blocks of 2097052 bytes.
> btape: btape.c:505 Wrote 1 EOF to "Drive-0" (/dev/nst2)
> btape: btape.c:856 Rewind OK.
> 23-May 14:54 btape JobId 0: Error: block.c:290 Volume data error at 0:0! 
> Block length 2097088 is insane (too large), probably due to a bad archive.
> btape: btape.c:868 Read block 1 failed! ERR=Input/output error
> 
> Why is it insane? :)

I found this in /src/stored/block.h:
   41 #define MAX_BLOCK_LENGTH  (1024*1024 + 1) /* this is a sort of sanity 
check */
   42 #define DEFAULT_BLOCK_SIZE (512 * 126)  /* 64,512 N.B. do not use 65,636 
here */

What's the reasoning behind MAX_BLOCK_LENGTH?

Also cced to bacula-devel in case that is more appropriate than bacula-users.

Regards,
-- 
Alex Chekholko 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users