User Manual

SCSI Commands Reference Manual, Rev. J 138
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4)
100b [b]
Yes Ye s [e]
LOGICAL BLOCK
GUARD
GRD_CHK = 1 LOGICAL BLOCK GUARD CHECK FAILED
GRD_CHK = 0 NO CHECK PERFORMED
LOGICAL BLOCK
APPLICATION TAG
NO CHECK PERFORMED
LOGICAL BLOCK
REFERENCE TAG
NO CHECK PERFORMED
No
[a]
No protection information available to transmit to the data-in buffer or for checking
101b -
111b
Reserved
[a] A read operation to a logical unit that supports protection information and has not been formatted with protection information shall
be terminated with CHECK CONDITION status with the sense key set to ILLEGAL REQUEST and the additional sense code set to
INVALID FIELD IN CDB.
[b] If the logical unit does not support protection information the requested command should be terminated with CHECK CONDITION
status with the sense key set to ILLEGAL REQUEST and the additional sense code set to INVALID FIELD IN CDB.
[c] If the device server has knowledge of the contents of the LOGICAL BLOCK APPLICATION TAG field, then the device server shall check
each logical block application tag. If the ATO bit in the Control mode page (see 5.3.12) is set to one, then this knowledge is acquired
from:
1) the EXPECTED LOGICAL BLOCK APPLICATION TAG field and the LOGICAL BLOCK APPLICATION TAG MASK field in the
CDB, if a READ (32) command
(see 3.19) is received by the device server;
2) the Application Tag mode page (see 5.3.6), if a command other than READ (32) is received by the device server, and
the ATMPE bit in the Control mode page (see 5.3.12) is set to one; or
3) a method not defined by this standard, if a command other than READ (32) is received by the device server, and the
ATMPE bit is set to zero.
[d] If an error is reported, the sense key shall be set to ABORTED COMMAND.
[e] Transmit protection information to the data-in buffer.
[f] If multiple errors occur, the selection of which error to report is not defined by this manual.
[g] See the Extended INQUIRY Data VPD page (see 5.4.9) for the definitions of the GRD_CHK bit, the APP_CHK bit,
and the REF_CHK bit.
[h] If the device server detects:
1) a LOGICAL BLOCK APPLICATION TAG field set to FFFFh and type 1 protection (see SBC-4) or type 2 protection
(see SBC-4) is enabled; or
2) a LOGICAL BLOCK APPLICATION TAG field set to FFFFh, LOGICAL BLOCK REFERENCE TAG field set to FFFF FFFFh,
and type 3 protection (see SBC-4) is enabled, then the device server shall not check any protection information in the
associated protection information interval.
[i] If type 1 protection is enabled, the device server checks the logical block reference tag by comparing it to the lower 4 bytes of the
LBA associated with the logical block.
If type 2 protection or type 3 protection is enabled, the device server checks the LOG-
ICAL BLOCK REFERENCE TAG if it has knowledge of the contents of the logical block reference tag field. If type 2 protec-
tion is enabled, then this knowledge may be acquired through the expected INITIAL LOGICAL BLOCK REFERENCE TAG
field in a READ (32) command (see 3.19). If type 3 protection is enabled, then the method for acquiring this knowledge is
not defined by
this manual.
[j] If the DPICZ bit in the Control mode page (see 5.3.12) is set to one, then protection information shall not be checked.
Table 98 RDPROTECT field (Sheet 2 of 2)
Code
Logical unit
formatted with
protection
information
Shall device server
transmit protection
information?
Field in protection
information [h]
Extended
INQUIRY Data
VPD page bit
value [g]
If check fails [d] [f],
additional sense code