User Manual

SCSI Commands Reference Manual, Rev. J 239
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4)
110b -
111b
Reserved
[a] A verify 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:
a) the EXPECTED LOGICAL BLOCK APPLICATION TAG field and the LOGICAL BLOCK APPLICATION TAG MASK field in the CDB, if a VERIFY
(32) command (see 3.58) is received by the device server;
b) the Application Tag mode page (see 5.3.6) if a command other than VERIFY (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
c) a method not defined by this standard, if a command other than VERIFY (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] If multiple errors occur, the selection of which error to report is not defined by this manual.
[f] 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.
[g] If the application client or device server detects a:
a) logical block application tag field set to FFFFh and type 1 protection or type 2 protection is enabled; or
b) logical block application tag field set to FFFFh, logical block reference tag field set to FFFF FFFFh, and type 3 protection
is enabled,
then the device server shall not check any protection information in the associated logical block.
[h] 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 logical
block reference tag if it has knowledge of the contents of the logical block reference tag field. If type 2 protection is
enabled, then this knowledge may be acquired through the expected initial logical block reference tag field in a VERIFY (32)
command (see 3.58). If type 3 protection is enabled, then the method for acquiring this knowledge is not defined by this
manual.
[i] 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 209 VRPROTECT field with BYTCHK field set to 01b or 11b - medium (Sheet 2 of 2)
Code
Logical unit formatted
with protection
information
Field in protection
information [g]
Extended INQUIRY
Data VPD page bit
value [f]
If check fails
[d] [e]
,
additional sense code