Table of Contents
Advertisement
Write Command
Data Integrity Validation—Write Operations
During write operations when DIV mode is enabled, all Write commands must have
a transfer length that includes both the user data and the appended 4 bytes of
Protection Information.
When in DIV mode the T10000 A and B tape drives strip away the PI data during
transfer from the controller data buffer to the tape drive.
On T10000C and T10000D tape drives, the PI data is written to the media.
If an error occurs during Write operations, and the drive detects a miscompare, it
reports it as a:
Check condition, with
Key = 04h (Hardware Error), and
ASC/ASCQ = 10 01h — Logical Block Guard Check Failed
This record is not written on the media.
Examples of when this may occur include:
• When transferring data for Write operations. As data passes from the Fibre
Channel FC protocol chip (if it supports the current PI method) to the controller
data buffer.
• If the drive is operating in Buffered mode, later when transferring the data to tape,
the PI data is checked and a deferred error occurs.
• If the drive is operating in Non Buffered mode, when transferring the data from
the controller data buffer to the tape, the PI data is checked.
For the Logical Block Guard Check error in buffered mode the error recovery procedure
is as follows:
• On T10000A or B: the trapped write data must be released with a Rewind or
Unload command, followed by repositioning of the tape to the last good record
and retrying the failed write.
• On T10000C or T10000D: the trapped write data can also be released by doing a
Space backwards then Space forwards, followed by retrying the failed record.
236 T10000: Interface Reference Manual
Note – Use the Mode Select command Page 0Ah, Subpage F0h, to
enable the DIV mode.
August 2016
Advertisement
Chapters
Table of Contents
