>>>>> On Tue, 20 Oct 2015 15:02:23 -0700, Mark D Strohm said:
>
> Hello Patti and Martin-
>
> Thank you for the replies.
>
> As I understand it, Bacula should have no problem with LTO hardware
> encryption because (once set) it is supposed to be transparent at the user
> level, the same as hardware compression. But apparently it is not perfectly
> transparent.
>
> I’m bringing the problem up on the Bacula list because I’m confident it can
> be worked around in software (mt and dd relate to the encrypted tape
> successfully), and changing the drive firmware isn’t really an option. But
> I’m not sure whether a simple configuration change is needed, or if I have to
> modify something in the Bacula programs.
>
> stenc does appear to be configuring the drive encryption properly. It can
> move the drive in-to and out-of all the modes I intend to use. It correctly
> reports the Key-label active in the drive, and reports mismatches with the
> Key-label on the tape.
>
> The system has been working without encryption for several months, using the
> mptspi and st Driver Modules.
>
> The system log shows only activity after the error. The Storage Daemon stops
> working actively when it reaches the second file, and reports an error after
> about ten minutes. Then there are log entries as the driver attempts to
> abort a task, fails, and resets the device.
>
> Oct 19 14:19:43 ccnback kernel: mptscsih: ioc0: attempting task abort!
> (sc=ffff8801b7682380)
> Oct 19 14:19:43 ccnback kernel: st 6:0:3:0: CDB:
> Oct 19 14:19:43 ccnback kernel: Read(6): 08 00 00 fc 00 00
> Oct 19 14:19:43 ccnback kernel: mptscsih: ioc0: task abort: FAILED (rv=2003)
> (sc=ffff8801b7682380)
> Oct 19 14:19:43 ccnback kernel: mptscsih: ioc0: attempting target reset!
> (sc=ffff8801b7682380)
> Oct 19 14:19:43 ccnback kernel: st 6:0:3:0: CDB:
> Oct 19 14:19:43 ccnback kernel: Read(6): 08 00 00 fc 00 00
> Oct 19 14:19:53 ccnback kernel: mptscsih: ioc0: WARNING - Issuing Reset from
> mptscsih_IssueTaskMgmt!! doorbell=0x24000000
> Oct 19 14:19:54 ccnback kernel: mptscsih: ioc0: target reset: SUCCESS
> (sc=ffff8801b7682380)
> Oct 19 14:19:54 ccnback kernel: st0: Error 80000 (driver bt 0x0, host bt 0x8).
> Oct 19 14:19:54 ccnback kernel: scsi target6:0:3: Beginning Domain Validation
> Oct 19 14:19:54 ccnback kernel: scsi target6:0:3: Ending Domain Validation
> Oct 19 14:19:54 ccnback kernel: scsi target6:0:3: FAST-80 WIDE SCSI 160.0
> MB/s DT (12.5 ns, offset 127)
> Oct 19 14:19:55 ccnback kernel: scsi target6:0:3: Beginning Domain Validation
> Oct 19 14:19:57 ccnback kernel: scsi target6:0:3: Ending Domain Validation
> Oct 19 14:19:57 ccnback kernel: scsi target6:0:3: FAST-80 WIDE SCSI 160.0
> MB/s DT (12.5 ns, offset 127)
I'm not an expert on this, but a problem that requires the driver to issue a
target reset suggests a bug in the driver or in the drive's firmware.
Have you tried smartctl or tapeinfo to get more information about the failure
from the drive (e.g. TapeAlert messages)?
__Martin
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
