Thanks for pointing me to it, I did not notice it was at the beginning. I had a look at the target response and regardless of what the initiator is expecting it has not handled the given response correctly.
Here is the sense data. [b]Additional Sense Code+Qualifier: Reported Luns Data Has Changed (0x3f0e)[/b] The correct action from the initiator should be to rescan the LUNS on this sense code and that is not what it actioned with. It blindly sends the same command again and that's not a good practice. Thus this is simply bad condition handling on the initiators part and not a COMSTAR response issue. Regards, Mike -- This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
