An SBC-2 question regarding persistent reservation.
ralphoweber at CompuServe.COM
Mon Aug 21 08:07:26 PDT 2000
* From the T10 Reflector (t10 at t10.org), posted by:
* Ralph Weber <ralphoweber at compuserve.com>
Ah yes, this question:
> A command that does not explicitly write the medium shall be checked
> for reservation conflicts before the command enters the current task
> state for the first time. Once the command has entered the current task
> state, it shall not be terminated with a Reservation Conflict due to a
> subsequent reservation. A command that explicitly writes the medium
> shall be checked for reservation conflicts before the device server
> modifies the medium or cache as a result of the command. Once the
> command has modified the medium, it shall not be terminated with a
> Reservation Conflict due to a subsequent reservation.
I've been wondering if the two requirements might relate to the possibility
that write data may be sent to the target in the same interconnect
tenancy as the CDB with the expectation that the target would buffer (cache)
the data until the reservations have been checked.
Note, I'm not suggesting that I know the answer only curious about a
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org
More information about the T10