Hello Kern-
Thanks for the reply. Something like that may be at the root of the problem,
but the drive does not report being in SysV mode. It shows only these options
set: buffer-writes, async-writes, read-ahead, can-bsr and scsi2logical.
The Tape Testing Tools and their debug modes were very
Hello,
In looking at your patch, I would guess that your tape drive is set in
SysV mode, which Bacula does not support. Bacula only supports Berkeley
tape conventions.
Have you worked through the Tape Testing chapter of the main manual? If
you have, I would find it very strange that the testin
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
