Jim, slightly off topic, I've noticed before that in the debug log, you sometimes do not get a '\n' at the end of a line.
And so you end up with what should be two lines, joined up end to end on one line. (This can occur under 'normal' operation.) I've assumed the cause is that in the code, someone just forgot to put in the '\n', but I've not actually checked this - maybe I should. You can see an example here in this post from last year: http://mail.opensolaris.org/pipermail/storage-discuss/2008-February/004878.html ..in this line: CON0 TargetName = iqn.1986-03.com.sun:02:d1c4c591-883e-697e-d9CON0 AuthMethod = None (The above IS one line, but Pipermail or Jive may word wrap it.) And note that the above in on and just after the 'TargetName' line, that you were commenting on in Frank's debug log. Going back to this particular problem, it does look like a crash immediately after the return from 'isns_enabled()' within the routine 'check_access()'. My only concern would be the possibly that DTrace is buffering up it's output, and not fully flushing out what has actually happended before the core dump. Although it is showing output on the other thread just after this point. But I don't know enough about how DTrace works to know if this could be an issue. Best Regards Nigel Smith -- This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
