spc-3 asymmetric lu access

Ralph Weber roweber at IEEE.org
Mon Nov 10 13:37:26 PST 2003


* From the T10 Reflector (t10 at t10.org), posted by:
* Ralph Weber <roweber at ieee.org>
*
Rich,

It seems to me that a device can always return BUSY status. A
device can be BUSY at anytime, just because it is ...well...
busy.

 From this perspective, list entry a) is simply stating the obvious.
Whereas list entry b) is confining its discussion to the case
where the device returns CHECK CONDITION status.

Regards,

.Ralph

Rich Ramos wrote:

>* From the T10 Reflector (t10 at t10.org), posted by:
>* Rich Ramos <t10 at RichRamos.com>
>*
>
>In section 5.7.5 of SPC-3 "Transitions between target port asymmetric 
>states"...
>
>Sub-section (a) gives two options of responses.  One is to return 
>BUSY and one is to return "LOGICAL UNIT NOT ACCESSIBLE, ASYMMETRIC 
>STATE TRANSITION"
>
>However...
>
>sub-section (b) only gives one possibility and that is to return 
>"LOGICAL UNIT NOT ACCESSIBLE, ASYMMETRIC STATE TRANSITION".
>
>
>This seems to be inconsistent.  It would seem like both should either 
>give two options (busy and the long one...) or both should only give 
>one option (just the long one).
>
>For the sake  of interoperability, can I suggest that we take out the 
>BUSY option for sub-section (a)?
>
>If, on the other hand, there is some technical reason to have BUSY in 
>section (a) then shouldn't it also be true for section (b)?  (hope 
>this isn't the case and that it can just be removed)
>
>-Rich 
>
>*
>* For T10 Reflector information, send a message with
>* 'info t10' (no quotes) in the message body to majordomo at t10.org
>
>
>  
>

*
* 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 mailing list