5.28RELEASE (6) Command (17h)
The RELEASE and the RESERVE commands are used for contention resolution in
Table
Bit | 7 | 6 | 5 |
| 4 |
| 3 |
| 2 |
| 1 | 0 |
Byte |
|
|
|
| ||||||||
|
|
|
|
|
|
|
|
|
|
|
| |
0 |
|
|
|
| Operation | Code (17h) |
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
1 |
| Reserved |
|
| 3rdPty |
| Third Party Device ID |
| Extent | |||
|
|
|
|
|
|
|
|
|
|
| ||
2 |
|
|
|
| Reservation | Identification |
|
|
|
| ||
|
|
|
|
|
|
|
|
|
|
|
| |
3 - 4 |
|
|
|
| Reserved |
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
5 |
|
|
|
| Control |
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Table | |
|
| |
Field | Description | |
|
| |
| Third Party Release allows an initiator to release a logical unit that was previously reserved. If the | |
| value in this field is 0, third party release is not requested. | |
3rdPty | When the value is 1, the drive releases the specified logical unit, but only if the reservation was | |
| ||
| made by the initiator using a | |
| device as specified in the Third Party Device ID field. | |
Third Party Device | Required if the 3rdPty bit is 1. This field specifies the SCSI ID (0 through 7 only) of the initiator | |
whose third party reservation is being released. (This field must be set if the initiator of the original | ||
ID | ||
third party RESERVE is the source of the RELEASE.) | ||
| ||
|
| |
Extent | The drive supports reservations only on entire logical units. The value must be 0. | |
|
| |
Reservation | Any value in this field is ignored by the drive. | |
Identification | ||
|
Note: Assuming that the RELEASE Command Descriptor Block is valid, the drive always returns a GOOD status for this command. An actual release only happens if the initiator has the unit reserved for itself or a
Maxtor Atlas 10K V |