PERSISTENT RESERVE IN
6.Command Specification
SONY AIT-3Ex drive SDX-800V series Ver.1.0
6-61
SCOPE:
The value in this field indicates whether a persistent reservation applies to an entire logical unit to an
element. The value in this filed are defined in table 6-58.
Table 6-58: PERSISTENT RESERVATION SCOPE Codes
Code Name
Description
0h
Logical Unit
Persistent reservation applies to the full logical unit
1h
Obsolete
2h
Element (not supported in this drive) Persistent reservation applies to the specified element
3h-fh Reserved
Reserved
Logical Unit:
A SCOPE value of Logical Unit indicates that the persistent reservation applies to the entire logical
unit. The Logical Unit scope shall be implemented by all device servers that implement PERSISTENT RESERVE
OUT.
Element:
A SCOPE filed value of Element indicates that the persistent reservation applies to the element of the
logical unit defined by the SCOPE-SPECIFIC Address field in the PERSISTENT RESERVE OUT parameter list.
The drive do not support it.
TYPE:
The value in the TYPE filed specify the characteristics of the persistent reservation being established for all
data blocks within the element or within the logical unit. Table 6-59 defines the characteristic of the different type
values. For each persistent reservation type, table 6-59 lists code value and describes the required device server
support. In this table, the description of required device server support is divided in two paragraphs. The first
paragraph defines the required handling for read operations. The second paragraph defines the required handling
for write operations.
Table 6-59: PERSISTENT RESERVATION TYPE Codes
Code Name
Description
0h
Obsolete
1h Write
Exclusive
Reads Shared:
Any application client on any initiator may execute tasks that request
transfers from the storage medium or cache of the logical unit to the initiator.
Writes Exclusive:
Any task from any initiator other than the initiator holding the
persistent reservation that requests a transfer from the initiator to the storage medium
or cache of the logical unit shall result in a reservation conflict.
2h
Obsolete
3h Exclusive
Access
Reads Exclusive:
Any task from any initiator other than the initiator holding the
persistent reservation that requests a transfer from the storage medium or cache of
the logical unit shall result in a reservation conflict.
Write Exclusive:
Any task from any initiator other than the initiator holding the
persistent reservation that requests a transfer from the initiator to the storage medium
or cache of the logical unit shall result in a reservation conflict.
4h
Obsolete
5h Write
Exclusive-
Registrants
Only
Reads Shared:
Any application client on any initiator may execute tasks that request
transfers from the storage medium or cache of the logical unit to the initiator.
Writes Exclusive:
Any task from any initiator other than the initiator holding the
persistent reservation that requests a transfer from the initiator to the storage medium
or cache of the logical unit shall result in a reservation conflict.
6h Exclusive
Access-
Registrants
Only (not
supported in
this drive)
Reads Exclusive:
A task that requests a transfer from the storage medium or cache
of the logical unit to an initiator that has not previously requested a REGISTER
service action with the drive shall result in a reservation conflict.
Write Exclusive:
Any task from any initiator other than the initiator holding the
persistent reservation that requests a transfer from the initiator to the storage medium
or cache of the logical unit shall result in a reservation conflict.
7h-Fh Reserved