Further to Andrey kuzmin's post, it would be interesting to see part of the initiator log from just before the line: "iscsid: Nop-out timedout after 15 seconds on connection 5:0 state (3). Dropping session." All subsequent lines are from the "kernel", (except the last) which is expected as it is just seeing the iscsi drive disappear. Are there any prior lines, from "iscsid", to give a clue to what the initiator was trying to do before the connection was lost. (Can you turn up the verbosity of messages from iscsid?)
It would be useful to have time's on the 'iscsisnoop.d' lines, which would help to relate it to the initiator log (assuming of course that the clocks on the initiator & the target are in sync). I'm not a DTrace expert, so I cannot tell you how, without some further research! I've done a Google on the error message: http://www.google.co.uk/search?hl=en&q=%22Nop-out+timedout+after%22+%22seconds+on+connection%22+state++%22Dropping+session.%22&btnG=Google+Search&meta= .. and it seems afew other people are seeing this, and with other targets. Mike Christe (lead developer of Open-iscsi initiator) explains: "So this means that we tried to ping a target and it did not reply for 15 seconds, so the iscsi initiator drops the session and tries to rebuild it." Regards Nigel Smith -- This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
