PERSISTENT RESERVE IN

6.Command Specification

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-60.

Table 6-60: PERSISTENT RESERVATION SCOPE Codes

Code

Name

Description

0h

Logical unit

Persistent reservation applies to the full logical unit

1h

Obsolete

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 will be implemented by all targets 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-61 defines the characteristic of the different type values. For each persistent reservation type, Table 6-61 lists code value and describes the required target support. In this table, the description of required target 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-61: PERSISTENT RESERVATION TYPE Codes

 

 

 

 

Code

Name

 

Description

0h

 

 

Obsolete

1h

Write

 

Reads Shared: Any application client on any initiator may execute tasks that

 

Exclusive

 

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 will result in a reservation conflict.

2h

 

 

Obsolete

3h

Exclusive

 

Reads Exclusive: Any task from any initiator other than the initiator holding the

 

Access

 

persistent reservation that requests a transfer from the storage medium or cache of

 

 

 

the logical unit will 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 will result in a reservation conflict.

4h

 

 

Obsolete

5h

Write

 

Reads Shared: Any application client on any initiator may execute tasks that

 

Exclusive-

 

request transfers from the storage medium or cache of the logical unit to the

 

Registrants

 

initiator.

 

Only

 

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 will result in a reservation conflict.

6h

Exclusive

 

Reads Exclusive: A task that requests a transfer from the storage medium or

 

Access-

 

cache of the logical unit to an initiator that has not previously requested a

 

Registrants

 

REGISTER service action with the drive will result in a reservation conflict.

 

Only (not

 

Write Exclusive: Any task from any initiator other than the initiator holding the

 

supported in

 

persistent reservation that requests a transfer from the initiator to the storage

 

this drive)

 

medium or cache of the logical unit will result in a reservation conflict.

7h-Fh

Reserved

 

 

SONY AIT-5 drive SDX-1100V series Ver.1.0

6-59

Page 113
Image 113
Sony SDX-1100V/R manual Persistent Reservation Scope Codes, Name Description, Persistent Reservation Type Codes