From 1a390f63de447cf7b98aaca146f697b30fd6e4fe Mon Sep 17 00:00:00 2001 From: Vladislav Bolkhovitin Date: Mon, 11 May 2009 17:26:17 +0000 Subject: [PATCH] - Error logging improved - Docs updates git-svn-id: http://svn.code.sf.net/p/scst/svn/trunk@842 d57e44dd-8a1f-0410-8b47-8ef2f437770f --- iscsi-scst/README | 7 ++++++- iscsi-scst/README_in-tree | 21 +++++++++++++++++++++ iscsi-scst/usr/iscsid.c | 2 ++ 3 files changed, 29 insertions(+), 1 deletion(-) diff --git a/iscsi-scst/README b/iscsi-scst/README index 88558a815..ff32d027e 100644 --- a/iscsi-scst/README +++ b/iscsi-scst/README @@ -152,7 +152,7 @@ file. Then, it might be helpful to increase level of logging. For kernel modules you should make the debug build, by either running "make -release2debug" if you work with SCST SVN tree, or by enable the +release2debug" if you work with SCST SVN tree, or by enabling the corresponding debug symbols (see below). If after looking on the logs the reason of your problem is still unclear @@ -183,6 +183,11 @@ consider to decrease TcpAckFrequency parameter to 1. See http://support.microsoft.com/kb/328890/ or google for "TcpAckFrequency" for more details. +2. See how to get the maximum throughput from iSCSI, for instance, at +http://virtualgeek.typepad.com/virtual_geek/2009/01/a-multivendor-post-to-help-our-mutual-iscsi-customers-using-vmware.html. +It's about VMware, but its recommendations apply to other environments +as well. + Compilation options ------------------- diff --git a/iscsi-scst/README_in-tree b/iscsi-scst/README_in-tree index afe9fde0c..a803c5b12 100644 --- a/iscsi-scst/README_in-tree +++ b/iscsi-scst/README_in-tree @@ -79,6 +79,22 @@ CAUTION: Working of target and initiator on the same host isn't fully ======= supported. See SCST README file for details. +Troubleshooting +--------------- + +If you have any problems, start troubleshooting from looking at the +kernel and system logs. In the kernel log iSCSI-SCST and SCST core send +their messages, in the system log iscsi-scstd sends its messages. In +most Linux distributions both those logs are put to /var/log/messages +file. + +Then, it might be helpful to increase level of logging. For kernel +modules you should make the debug build by enabling CONFIG_SCST_DEBUG. + +If after looking on the logs the reason of your problem is still unclear +for you, report to SCST mailing list scst-devel@lists.sourceforge.net. + + Work if target's backstorage or link is too slow ------------------------------------------------ @@ -103,6 +119,11 @@ consider to decrease TcpAckFrequency parameter to 1. See http://support.microsoft.com/kb/328890/ or google for "TcpAckFrequency" for more details. +2. See how to get the maximum throughput from iSCSI, for instance, at +http://virtualgeek.typepad.com/virtual_geek/2009/01/a-multivendor-post-to-help-our-mutual-iscsi-customers-using-vmware.html. +It's about VMware, but its recommendations apply to other environments +as well. + Compilation options ------------------- diff --git a/iscsi-scst/usr/iscsid.c b/iscsi-scst/usr/iscsid.c index 0b2a1de03..f4348a11b 100644 --- a/iscsi-scst/usr/iscsid.c +++ b/iscsi-scst/usr/iscsid.c @@ -784,6 +784,7 @@ static void cmnd_exec_login(struct connection *conn) return; init_err: + log_error("Initiator %s error", conn->initiator); rsp->flags = 0; rsp->status_class = ISCSI_STATUS_INITIATOR_ERR; rsp->status_detail = ISCSI_STATUS_INIT_ERR; @@ -791,6 +792,7 @@ init_err: return; auth_err: + log_error("Authentication of initiator %s failed", conn->initiator); rsp->flags = 0; rsp->status_class = ISCSI_STATUS_INITIATOR_ERR; rsp->status_detail = ISCSI_STATUS_AUTH_FAILED;