Just to follow up, I did find a workaround for the I/O errors with LTO hardware
encryption: At the end of a tape file, space a record forward, then a record
back (code below).
I have not found the actual cause of the problem. It is most likely with the
vendor firmware for that particular IBM LTO-4 model. But the workaround does
permit both verifies and restores to work properly with encrypted tapes.
-Mark-
bacula-7.0.5
*** block.c.orig 2014-07-29 09:31:22.000000000 -0700
--- block.c 2015-11-13 14:16:04.000000000 -0800
***************
*** 441,446 ****
--- 441,452 ----
} else {
Mmsg3(dev->errmsg, _("Read zero bytes Vol=%s at %lld on device
%s.\n"),
dev->VolCatInfo.VolCatName, pos, dev->print_name());
+ if (dev->fsr(1)) { /* to deal with the encrypted eof jams,
forward space one record */
+ dev->bsr(1); /* if that works without error, back space
into position */
+ } else { /* if it throws an error ... */
+ dev->set_ateof(); /* set the ateof flag to trigger the eom
detection below */
+ dev->file--; /* and reset the file number */
+ }
}
dev->block_num = 0;
block->read_len = 0;
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
