Chris, I checked the latest snoop file, and I am not seeing any difference in the login response packet from the target. I would have expected to see some additional key/value pairs if the 'fixed' target was running. (That is my understanding of what it does, but I have not tested it for myself) The rest of the trace looks very similar with the same 'hang' by the target after the first 'read' by the initiator.
It seems to me that something must have gone wrong in how you installed the new target daemon. I think maybe what has happened is that Andrew has supplied you with a iscsitgtd for a 64-bit kernel architecture (amd64), but that you are using a 32-bit kernel (i386). I think you can confirm your architecture with the command 'isainfo -kv'. So run that & report back here. Maybe another issue is that you are using build 'snv_76' of the kernel and I suspect that Andrew's target is for an older build. If I'm right on either/both these points, then this could explain the 'weirdness '. I think what we need is a iscsitgt compiled for the architecture and the same build that you are running. I'm not sure how to do the compile myself, and I think the iscsitgtd that Andrew supplied was compiled by Rick McNeal. (Rick was the original author of the Solaris iscsi target, but he is no longer working for Sun.) I would like to be able to compile the iscsitgtd myself. Maybe with some spare time, I can figure out how to do it. Now that many of you USA people are back from your thanksgiving break, maybe other people will jump in with opinions & advice... Best Regards Nigel Smith This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
