
RELEASE | 6.Command Specification |
6.18.RELEASE (6/10) 17h and 57h
|
|
| RELEASE( 6) CDB format |
|
| ||||||
|
|
|
|
|
|
| 3 |
|
|
|
|
Bit | 7 | 6 | 5 | 4 |
|
|
| 2 | 1 | 0 | |
Byte |
|
|
|
|
|
|
|
|
|
|
|
0 |
|
|
| Operation |
| Code (17h) |
|
|
| ||
1 |
| Reserved |
|
|
|
|
|
| Obsolete |
|
|
2 |
|
|
| Reserved |
|
|
|
|
| ||
3 |
|
|
| Reserved |
|
|
|
|
| ||
4 |
|
|
| Reserved |
|
|
|
|
| ||
5 |
|
|
| Control |
|
|
|
|
| ||
|
|
| RELEASE (10) CDB format |
|
| ||||||
|
|
|
|
|
|
| 3 |
|
|
| |
Bit | 7 | 6 | 5 | 4 |
|
|
| 2 | 1 | 0 | |
Byte |
|
|
|
|
|
|
|
|
|
|
|
0 |
|
|
| Operation |
| Code (57h) |
|
|
| ||
1 |
| Reserved |
| 3rdPty |
|
| Reserved | LongID | Obsolete | ||
2 |
|
|
| Obsolete |
|
|
|
|
| ||
3 |
|
|
| Third Party Device ID |
|
| |||||
4 |
|
|
| Reserved |
|
|
|
|
| ||
5 |
|
|
| Reserved |
|
|
|
|
| ||
6 |
|
|
| Reserved |
|
|
|
|
| ||
|
|
| Parameter List Length |
|
| ||||||
9 |
|
|
| Control |
|
|
|
|
|
This RELEASE command releases the drive if it was reserved by the requesting initiator using a RESERVE (6/10) command and is still in the reserved state. See PERSISTENT RESERVE OUT/IN for an alternate reservation system. This command cannot release a reservation generated by the PERSISTENT RESERVE OUT command.
Third party reservation management operations are only allowed using RESERVE (10) and RELEASE (10). Logical unit reservation management operations are allowed using RESERVE (6/10) and RELEASE (6/10).
3rdPty: The
If the 3rdPty bit is ZERO, then the
If the 3rdPty bit is ONE, the Logical Unit releases the specified logical unit, but only if the initiator, 3rdPty bit, and Third Party Device ID fields (in CDB or in Parameter List) are identical when compared to the values used in the RESERVE (10) command that established the reservation.
Long ID: If the Long ID bit is set to 1b and the Parameter List Length is 8, the parameter list contains the eight bytes of the device ID of the Third Party Device ID.
If the 3rdPty bit is zero, the LONGID bit field is ignored.
Third Party Device ID: If the Third Party Device ID value that is connected with the reservation release is equal to or smaller than 255 (FFh), the LongID field may be 0b and the Third Party Device ID value is sent in this field.
The contents of the Third Party Device ID field in the CDB is ignored when LongID = 1b; Note: If the Third Party Device ID value is greater than 255 (FFh), LongID must be set to 1b.
SONY |