Hi,
I'm using a LTO-4 autochanger with a bacula-sd (v2.4.2) configured since
about one or two months with:
Maximum Block Size = 2097152
When I configured this setting I didn't get any SD or director warnings
or issues (or at least none that I could see).
Today I wanted to restore a full backup of a client that crashed hard.
I got the following error:
12-Nov 12:08 backup-sd JobId 2357: Ready to read from volume "ACM504L4"
on device "LTO4" (/dev/nst0).
12-Nov 12:08 backup-sd JobId 2357: Forward spacing Volume "ACM504L4" to
file:block 43:16.
12-Nov 12:09 backup-sd JobId 2357: Error: block.c:290 Volume data error
at 43:16! Block length 2097152 is insane (too large), probably due to a
bad archive.
Looking to block.c around line 290, I see:
/* Sanity check */
if (block_len > MAX_BLOCK_SIZE) {
dev->dev_errno = EIO;
MAX_BLOCK_SIZE is a constant whose value is: 1024*1024+1, which is
smaller than what I configured.
Is there really a limit on the maximum size of a block?
The documentation doesn't seem to say this.
Maybe some of the developper should change the documentation to indicate
that there is indeed a limit and check at sd start that the currently
given maximum block size is under this limit?
I can file a bug report if needed. Should I?
Anyway, I increased the value of this constant and I could restore this
full jobs without any issue (ok that wasn't so straightforward, but I
finally could restore the job).
Thanks,
--
Brice Figureau <[EMAIL PROTECTED]>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
