Re: Connection Errors
I have now changed the following, correct ? ## node.conn[0].timeo.noop_out_interval = 5 node.conn[0].timeo.noop_out_interval = 0 node.conn[1].timeo.noop_out_interval = 0 # node.conn[0].timeo.noop_out_timeout = 5 node.conn[0].timeo.noop_out_timeout = 0 node.conn[1].timeo.noop_out_timeout = 0 I noticed this: May 6 08:52:22 manjula iscsid: connection2:0 is operational now May 6 08:52:22 manjula iscsid: connection1:0 is operational now Should the above changes instead be: node.conn[1].xxx node.conn[2].xxx I still see the same errors though: May 6 09:07:06 manjula klogd: connection1:0: ping timeout of 5 secs expired, last rx 4636947795, last ping 4636942795, now 4636950295 May 6 09:07:06 manjula klogd: connection1:0: detected conn error (1011) May 6 09:07:07 manjula iscsid: Kernel reported iSCSI connection 1:0 error (1011) state (3) May 6 09:07:10 manjula iscsid: connection1:0 is operational after recovery (1 attempts) May 6 09:08:11 manjula klogd: connection1:0: ping timeout of 5 secs expired, last rx 4636964045, last ping 4636960295, now 4636966545 May 6 09:08:11 manjula klogd: connection1:0: detected conn error (1011) May 6 09:08:12 manjula iscsid: Kernel reported iSCSI connection 1:0 error (1011) state (3) May 6 09:08:15 manjula iscsid: connection1:0 is operational after recovery (1 attempts) May 6 09:08:41 manjula klogd: connection1:0: ping timeout of 5 secs expired, last rx 4636971545, last ping 4636970295, now 4636974045 May 6 09:08:41 manjula klogd: connection1:0: detected conn error (1011) May 6 09:08:42 manjula iscsid: Kernel reported iSCSI connection 1:0 error (1011) state (3) May 6 09:08:45 manjula iscsid: connection1:0 is operational after recovery (1 attempts) May 6 09:09:49 manjula klogd: connection1:0: ping timeout of 5 secs expired, last rx 4636988378, last ping 4636977795, now 4636990878 May 6 09:09:49 manjula klogd: connection1:0: detected conn error (1011) May 6 09:09:49 manjula iscsid: Kernel reported iSCSI connection 1:0 error (1011) state (3) May 6 09:09:52 manjula iscsid: connection1:0 is operational after recovery (1 attempts) May 6 09:10:36 manjula klogd: connection1:0: ping timeout of 5 secs expired, last rx 4637000296, last ping 4637000296, now 4637002796 May 6 09:10:36 manjula klogd: connection1:0: detected conn error (1011) May 6 09:10:37 manjula iscsid: Kernel reported iSCSI connection 1:0 error (1011) state (3) May 6 09:10:40 manjula iscsid: connection1:0 is operational after recovery (1 attempts) There seem to be about one minute between the failures. One observation, it's always connection1:0 that fails. Both target ports are connected to the same switch. Furthermore, are there supposed to as many processes as this ? root 104 2 0 Apr20 ?00:00:00 [scsi_eh_0] root 124 2 0 Apr20 ?00:00:00 [scsi_eh_1] root 125 2 0 Apr20 ?00:00:00 [scsi_eh_2] root 126 2 0 Apr20 ?00:00:00 [scsi_eh_3] root 127 2 0 Apr20 ?00:00:00 [scsi_eh_4] root 134 2 0 Apr20 ?00:00:00 [scsi_eh_5] root 135 2 0 Apr20 ?00:00:00 [scsi_eh_6] root 9580 2 0 May05 ?00:00:00 [scsi_eh_24] root 9581 2 0 May05 ?00:00:00 [scsi_wq_24] root 9583 2 0 May05 ?00:00:00 [scsi_eh_25] root 9584 2 0 May05 ?00:00:00 [scsi_wq_25] root 16981 2 0 08:35 ?00:00:00 [scsi_eh_26] root 16982 2 0 08:35 ?00:00:00 [scsi_wq_26] root 16984 2 0 08:35 ?00:00:00 [scsi_eh_27] root 16985 2 0 08:35 ?00:00:00 [scsi_wq_27] root 18289 2 0 Apr21 ?00:00:00 [scsi_eh_10] root 18290 2 0 Apr21 ?00:00:00 [scsi_wq_10] root 18369 2 0 Apr21 ?00:00:00 [scsi_eh_11] root 18370 2 0 Apr21 ?00:00:00 [scsi_wq_11] root 18448 2 0 08:52 ?00:00:00 [iscsi_eh] root 18517 1 0 08:52 ?00:00:00 /sbin/iscsid -c /etc/ iscsi/iscsid.conf -p /var/run/iscsi.pid root 18518 1 0 08:52 ?00:00:00 /sbin/iscsid -c /etc/ iscsi/iscsid.conf -p /var/run/iscsi.pid root 18547 2 0 08:52 ?00:00:00 [scsi_eh_28] root 18548 2 0 08:52 ?00:00:00 [scsi_wq_28] root 18549 2 0 08:52 ?00:00:00 [iscsi_scan_28] root 18550 2 0 08:52 ?00:00:00 [scsi_eh_29] root 18551 2 0 08:52 ?00:00:00 [scsi_wq_29] root 18552 2 0 08:52 ?00:00:00 [iscsi_scan_29] root 18719 2 0 Apr21 ?00:00:00 [scsi_eh_12] root 18720 2 0 Apr21 ?00:00:02 [scsi_wq_12] root 18722 2 0 Apr21 ?00:00:00 [scsi_eh_13] root 18723 2 0 Apr21 ?00:00:00 [scsi_wq_13] root 19272 15942 0 09:15 pts/000:00:00 grep scsi root 25657 2 0 May01 ?00:00:00 [scsi_eh_14] root 25659 2 0 May01 ?00:00:00 [scsi_wq_14] root 25663 2 0 May01 ?
Re: Target address redirect ignored
> I am working on a patch. Thank's Mike! I'll keep an eye on this thread. regards, Lukasz --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Feature Request: dynamically update max_lun
Stefan de Konink wrote: > Unlike the scsi module paramater max_luns, iscsi's max_lun cannot be set > on the fly. It requires unloading the module and loading it again. > > Would it be possible to add the functionality? > Yeah, we can do that. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Connection Errors
swejis wrote: > I have now changed the following, correct ? > > ## node.conn[0].timeo.noop_out_interval = 5 > node.conn[0].timeo.noop_out_interval = 0 > node.conn[1].timeo.noop_out_interval = 0 > > # node.conn[0].timeo.noop_out_timeout = 5 > node.conn[0].timeo.noop_out_timeout = 0 > node.conn[1].timeo.noop_out_timeout = 0 > > I noticed this: > > May 6 08:52:22 manjula iscsid: connection2:0 is operational now > May 6 08:52:22 manjula iscsid: connection1:0 is operational now > > Should the above changes instead be: > > node.conn[1].xxx > node.conn[2].xxx No. The first numnber in connectionX:Y is the session number. > > I still see the same errors though: > > May 6 09:07:06 manjula klogd: connection1:0: ping timeout of 5 secs > expired, last rx 4636947795, last ping 4636942795, now 4636950295 It looks the value did not get picked up. Forget I asked you to do this ok? We do not need it. Could you just try http://open-iscsi.org/bits/open-iscsi-2.0-869.1.test1.tar.gz Remove the old iscsi tools (I think in suse the package is named open-iscsi). Do rpm -e open-iscsi Now build this test package http://open-iscsi.org/bits/open-iscsi-2.0-869.1.test1.tar.gz with extra debugging: Build it with make DEBUG_SCSI=1 make DEBUG_SCSI=1 install > > Furthermore, are there supposed to as many processes as this ? > You are going to get a scsi_eh and a scsi_wq and a iscsi_scan thread per session/target. Some targets do a target per device/LU/LUN and in that case you would see a lot. If you run iscsiadm -m session we can see what is up. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Connection Errors
OK, removed iscsi package. Compiled new package (added suse-parameters recommended from readme file) make DEBUG_SCSI=1 KSRC=/usr/src/linux-2.6.25-rc9-17 KBUILD_OUTPUT=/usr/ src/linux-obj/x86_64/default Compilation completeOutput file --- Built iSCSI Open Interface module: kernel/scsi_transport_iscsi.ko Built iSCSI library module: kernel/libiscsi.ko Built iSCSI over TCP kernel module: kernel/iscsi_tcp.ko Built iSCSI daemon: usr/iscsid Built management application: usr/iscsiadm make DEBUG_SCSI=1 install make -C kernel install_kernel make[1]: Entering directory `/opt/src/open-iscsi-2.0-869.1.test1/ kernel' make[1]: *** No rule to make target `linux_2_6_', needed by `kernel_check'. Stop. make[1]: Leaving directory `/opt/src/open-iscsi-2.0-869.1.test1/ kernel' make: *** [install_kernel] Error 2 Am I doing something wrong? Do I have to prepare the kernel source tree somehow? I just installed the sources. rgds Jonas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: scsi_transport_iscsi versions
> is a little scary. It looks like you might have multiple versions of > userspace running/installed (open-iscsi-2.0-865.15 and 2.0-869). That we > do not support. Make sure you have one version of userspace installed > (do whereis for iscsid, iscsiadm iscsistart to see if there are multiple > copies of programs). seems like there is only a single instance of each: whereis iscsid iscsid: /sbin/iscsid /usr/share/man/man8/iscsid.8.gz [EMAIL PROTECTED]:/lib/modules/2.6.24-16-generic/kernel/drivers/scsi# whereis iscsiadm iscsiadm: /sbin/iscsiadm /usr/share/man/man8/iscsiadm.8.gz [EMAIL PROTECTED]:/lib/modules/2.6.24-16-generic/kernel/drivers/scsi# whereis iscsistart iscsistart: /sbin/iscsistart [EMAIL PROTECTED]:/lib/modules/2.6.24-16-generic/kernel/drivers/scsi# would you recommend that I should just remove these and reinstall? ... Just to be certain, this is the right binary for for Ubuntu on AMD 64 right? http://packages.ubuntu.com/hardy/amd64/open-iscsi/download .. - a. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: scsi_transport_iscsi versions
a s p a s i a wrote: >> is a little scary. It looks like you might have multiple versions of >> userspace running/installed (open-iscsi-2.0-865.15 and 2.0-869). That we >> do not support. Make sure you have one version of userspace installed >> (do whereis for iscsid, iscsiadm iscsistart to see if there are multiple >> copies of programs). > > seems like there is only a single instance of each: > > whereis iscsid > iscsid: /sbin/iscsid /usr/share/man/man8/iscsid.8.gz > [EMAIL PROTECTED]:/lib/modules/2.6.24-16-generic/kernel/drivers/scsi# whereis > iscsiadm > iscsiadm: /sbin/iscsiadm /usr/share/man/man8/iscsiadm.8.gz > [EMAIL PROTECTED]:/lib/modules/2.6.24-16-generic/kernel/drivers/scsi# > whereis iscsistart > iscsistart: /sbin/iscsistart > [EMAIL PROTECTED]:/lib/modules/2.6.24-16-generic/kernel/drivers/scsi# > > would you recommend that I should just remove these and reinstall? Yeah. > ... Just to be certain, this is the right binary for for Ubuntu on AMD > 64 right? > > http://packages.ubuntu.com/hardy/amd64/open-iscsi/download > I think so. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Connection Errors
swejis wrote:
> OK, removed iscsi package.
>
> Compiled new package (added suse-parameters recommended from readme
> file)
>
> make DEBUG_SCSI=1 KSRC=/usr/src/linux-2.6.25-rc9-17 KBUILD_OUTPUT=/usr/
> src/linux-obj/x86_64/default
>
>
> Compilation completeOutput file
> ---
> Built iSCSI Open Interface module: kernel/scsi_transport_iscsi.ko
> Built iSCSI library module: kernel/libiscsi.ko
> Built iSCSI over TCP kernel module: kernel/iscsi_tcp.ko
> Built iSCSI daemon: usr/iscsid
> Built management application: usr/iscsiadm
>
> make DEBUG_SCSI=1 install
> make -C kernel install_kernel
> make[1]: Entering directory `/opt/src/open-iscsi-2.0-869.1.test1/
> kernel'
> make[1]: *** No rule to make target `linux_2_6_', needed by
> `kernel_check'. Stop.
> make[1]: Leaving directory `/opt/src/open-iscsi-2.0-869.1.test1/
> kernel'
> make: *** [install_kernel] Error 2
>
> Am I doing something wrong? Do I have to prepare the kernel source
> tree somehow? I just installed the sources.
>
Apply the attached patch.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---
--- Begin Message ---
These are some Makefile updates to build on system without
kernel-sources installed.
And cleanups to have it build properly on SUSE systems.
Signed-off-by: Hannes Reinecke <[EMAIL PROTECTED]>
---
Makefile|9 ++---
kernel/Makefile | 21 +
usr/Makefile|4 +++-
3 files changed, 26 insertions(+), 8 deletions(-)
diff --git a/Makefile b/Makefile
index 7661daa..e6dc435 100644
--- a/Makefile
+++ b/Makefile
@@ -32,9 +32,12 @@ all:
@echo
@echo "Compilation completeOutput file"
@echo "--- "
- @echo "Built iSCSI Open Interface module:
kernel/scsi_transport_iscsi.ko"
- @echo "Built iSCSI library module: kernel/libiscsi.ko"
- @echo "Built iSCSI over TCP kernel module: kernel/iscsi_tcp.ko"
+ @if [ -f kernel/scsi_transport_iscsi.ko ] ; then \
+ echo "Built iSCSI Open Interface module:
kernel/scsi_transport_iscsi.ko"; fi
+ @if [ -f kernel/libiscsi.ko ] ; then \
+ echo "Built iSCSI library module: kernel/libiscsi.ko"; fi
+ @if [ -f kernel/iscsi_tcp.ko ] ; then \
+ echo "Built iSCSI over TCP kernel module: kernel/iscsi_tcp.ko"; fi
@echo "Built iSCSI daemon: usr/iscsid"
@echo "Built management application: usr/iscsiadm"
@echo
diff --git a/kernel/Makefile b/kernel/Makefile
index 7281a60..8209473 100644
--- a/kernel/Makefile
+++ b/kernel/Makefile
@@ -32,11 +32,16 @@ V ?= 0
# eg to compile for a kernel that you aren't currently running
KERNELRELEASE ?= $(shell uname -r)
KSRC ?= /lib/modules/$(KERNELRELEASE)/build
+KSRC := $(shell test -f $(KSRC)/Makefile || echo "")
KBUILD_OUTPUT ?=
# this is the basic Kbuild invocation, just append your make target
KBUILD_BASE = +$(MAKE) -C $(KSRC) M=`pwd` KBUILD_OUTPUT=$(KBUILD_OUTPUT)
$(KARCH) V=$(V)
-all: kernel_check
+all: kernel_src
+
+kernel_src: $(shell test -n "$(KSRC)" && echo has_kernel_src)
+
+has_kernel_src: kernel_check
$(KBUILD_BASE) modules
# BEGIN code for kernel_check and source patching
@@ -59,9 +64,11 @@ cur_patched=cur_patched
# check to see if code is unpatched
unpatch_code=$(shell test -e $(cur_patched) && echo do_unpatch_code )
-KSUBLEVEL = $(shell cat $(KSRC)/Makefile | awk -F= '/^SUBLEVEL =/ {print $$2}'
| \
+KSUBLEVEL = $(shell cat $(KSRC)/Makefile 2> /dev/null | awk -F= '/^SUBLEVEL =/
{print $$2}' | \
sed 's/^[ \t]*//;s/[ \t]*$$//')
+KSUBLEVEL?=$(shell echo $(KERNELRELEASE) | sed -n
's/.\..\.\([[:digit:]]*\)\..*/\1/p')
+
KERNEL_TARGET=linux_2_6_$(KSUBLEVEL)
kernel_check: $(KERNEL_TARGET)
@@ -126,7 +133,11 @@ has_24_patch: $(24_patch)
# END code for kernel_check and source patching =
-clean: $(unpatch_code)
+clean: clean_kernel_src
+
+clean_kernel_src: $(shell test -n "$(KSRC)" && echo has_clean_kernel_src)
+
+has_clean_kernel_src: $(unpatch_code)
$(KBUILD_BASE) clean
rm -f Module.symvers
@@ -165,7 +176,9 @@ ko = $(patsubst %.o,%.ko,$(obj-m))
$(ko): all
# now the actual command
-install_kernel: $(ko)
+install_kernel: $(shell test -n "$(KSRC)" && echo install_kernel_obj);
+
+install_kernel_obj: $(ko)
$(KBUILD_BASE) modules_install INSTALL_MOD_DIR=$(INSTALL_MOD_DIR)
INSTALL_MOD_PATH=$(INSTALL_MOD_PATH)
dpkg_divert:
diff --git a/usr/Makefile b/usr/M
Re: Connection Errors
I'm sorry Mike but i'm uncertain what to copy. Tried to look and compare against your previously attached patch but with no success. manjula:/opt/src/open-iscsi-2.0-869.1.test1 # patch < iscsi.patch patching file Makefile Hunk #1 FAILED at 32. 1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej patching file Makefile Hunk #1 FAILED at 32. Hunk #2 FAILED at 64. Hunk #3 FAILED at 133. Hunk #4 FAILED at 176. 4 out of 4 hunks FAILED -- saving rejects to file Makefile.rej patching file Makefile Hunk #1 FAILED at 7. 1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej May I kindly ask you to attach this patch as you did with the other one ? Thanks Jonas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Connection Errors
swejis wrote:
> I'm sorry Mike but i'm uncertain what to copy. Tried to look and
> compare against your previously attached patch but with no success.
>
> manjula:/opt/src/open-iscsi-2.0-869.1.test1 # patch < iscsi.patch
> patching file Makefile
> Hunk #1 FAILED at 32.
> 1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej
> patching file Makefile
> Hunk #1 FAILED at 32.
> Hunk #2 FAILED at 64.
> Hunk #3 FAILED at 133.
> Hunk #4 FAILED at 176.
> 4 out of 4 hunks FAILED -- saving rejects to file Makefile.rej
> patching file Makefile
> Hunk #1 FAILED at 7.
> 1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej
>
> May I kindly ask you to attach this patch as you did with the other
> one ?
>
Ok try the attached.
from /opt/src/open-iscsi-2.0-869.1.test1 do
patch -p1 -i ../path-to-patch/suse-makefile-fix.patch
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---
diff -aurp open-iscsi-2.0-869.1.test1/kernel/Makefile open-iscsi-2.0-869.1.test1.tmp/kernel/Makefile
--- open-iscsi-2.0-869.1.test1/kernel/Makefile 2008-04-09 19:12:58.0 -0500
+++ open-iscsi-2.0-869.1.test1.tmp/kernel/Makefile 2008-05-06 13:26:17.0 -0500
@@ -32,11 +32,16 @@ V ?= 0
# eg to compile for a kernel that you aren't currently running
KERNELRELEASE ?= $(shell uname -r)
KSRC ?= /lib/modules/$(KERNELRELEASE)/build
+KSRC := $(shell test -f $(KSRC)/Makefile || echo "")
KBUILD_OUTPUT ?=
# this is the basic Kbuild invocation, just append your make target
KBUILD_BASE = +$(MAKE) -C $(KSRC) M=`pwd` KBUILD_OUTPUT=$(KBUILD_OUTPUT) $(KARCH) V=$(V)
-all: kernel_check
+all: kernel_src
+
+kernel_src: $(shell test -n "$(KSRC)" && echo has_kernel_src)
+
+has_kernel_src: kernel_check
$(KBUILD_BASE) modules
# BEGIN code for kernel_check and source patching
@@ -59,9 +64,11 @@ cur_patched=cur_patched
# check to see if code is unpatched
unpatch_code=$(shell test -e $(cur_patched) && echo do_unpatch_code )
-KSUBLEVEL = $(shell cat $(KSRC)/Makefile | awk -F= '/^SUBLEVEL =/ {print $$2}' | \
+KSUBLEVEL = $(shell cat $(KSRC)/Makefile 2> /dev/null | awk -F= '/^SUBLEVEL =/ {print $$2}' | \
sed 's/^[ \t]*//;s/[ \t]*$$//')
+KSUBLEVEL?=$(shell echo $(KERNELRELEASE) | sed -n 's/.\..\.\([[:digit:]]*\)\..*/\1/p')
+
KERNEL_TARGET=linux_2_6_$(KSUBLEVEL)
kernel_check: $(KERNEL_TARGET)
@@ -126,7 +133,11 @@ has_24_patch: $(24_patch)
# END code for kernel_check and source patching =
-clean: $(unpatch_code)
+clean: clean_kernel_src
+
+clean_kernel_src: $(shell test -n "$(KSRC)" && echo has_clean_kernel_src)
+
+has_clean_kernel_src: $(unpatch_code)
$(KBUILD_BASE) clean
rm -f Module.symvers
@@ -165,7 +176,9 @@ ko = $(patsubst %.o,%.ko,$(obj-m))
$(ko): all
# now the actual command
-install_kernel: $(ko)
+install_kernel: $(shell test -n "$(KSRC)" && echo install_kernel_obj);
+
+install_kernel_obj: $(ko)
$(KBUILD_BASE) modules_install INSTALL_MOD_DIR=$(INSTALL_MOD_DIR) INSTALL_MOD_PATH=$(INSTALL_MOD_PATH)
dpkg_divert:
diff -aurp open-iscsi-2.0-869.1.test1/Makefile open-iscsi-2.0-869.1.test1.tmp/Makefile
--- open-iscsi-2.0-869.1.test1/Makefile 2008-04-09 19:12:58.0 -0500
+++ open-iscsi-2.0-869.1.test1.tmp/Makefile 2008-05-06 13:26:17.0 -0500
@@ -32,9 +32,12 @@ all:
@echo
@echo "Compilation completeOutput file"
@echo "--- "
- @echo "Built iSCSI Open Interface module: kernel/scsi_transport_iscsi.ko"
- @echo "Built iSCSI library module: kernel/libiscsi.ko"
- @echo "Built iSCSI over TCP kernel module: kernel/iscsi_tcp.ko"
+ @if [ -f kernel/scsi_transport_iscsi.ko ] ; then \
+ echo "Built iSCSI Open Interface module: kernel/scsi_transport_iscsi.ko"; fi
+ @if [ -f kernel/libiscsi.ko ] ; then \
+ echo "Built iSCSI library module: kernel/libiscsi.ko"; fi
+ @if [ -f kernel/iscsi_tcp.ko ] ; then \
+ echo "Built iSCSI over TCP kernel module: kernel/iscsi_tcp.ko"; fi
@echo "Built iSCSI daemon: usr/iscsid"
@echo "Built management application: usr/iscsiadm"
@echo
diff -aurp open-iscsi-2.0-869.1.test1/usr/Makefile open-iscsi-2.0-869.1.test1.tmp/usr/Makefile
--- open-iscsi-2.0-869.1.test1/usr/Makefile 2008-04-09 19:12:58.0 -0500
+++ open-iscsi-2.0-869.1.test1.tmp/usr/Makefile 2008-05-06 13:26:17.0 -0500
@@ -7,9 +7,11 @@ OSNAME=$(shell uname -s)
KERNELRELEASE ?= $(shell uname -r)
KSRC ?= /lib/modules/$(KERNELRELEASE)/build
-KSUBLEVEL=$(shell cat $(KSRC)/Makefile | awk -F= '/^SUBLEVEL =/ {print $$2}' | \
+KSUBLEVEL=$(shell cat $(KSRC)/Makefile 2> /dev/null | awk
Re: scsi_transport_iscsi versions
aspasia wrote: > Hello, > > I have 2 installs of Ubuntu - one i686 and the other AMD64; I am > testing my AMD64 installation to boot iscsi root and found that it got > stuck during boot ... which let me to realize that it had an older > version of a module: This is a known bug in Ubuntu Hardy.. I just hit it today also: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/218215 Install the newer kernel from the hardy proposed-updates repository and it fixes the problem. Jesper -- Jesper --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Connection Errors
OK, were back in business. Built and installed the debug-initiator. The [scsi_eh_xx] scsi_wq_xx] processes, there are about 60 of those before I have even started open-iscsi, zombies ? May 6 21:03:53 manjula iscsid: connection3:0 is operational now May 6 21:03:53 manjula iscsid: connection4:0 is operational now 3 and 4 now, could this be caused by those processes ? I would have expected this version to be very noisy log-wise, however I have stressed the disk quite alot now and have not seen anything in the log. Performance actually also looks better. 3GB in 40 sec, that is far better than before. Those processes, could I just shut everything down and kill the remaining ? Rgds Jonas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: scsi_transport_iscsi versions
> > This is a known bug in Ubuntu Hardy.. I just hit it today also: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/218215 > > Install the newer kernel from the hardy proposed-updates repository and it > fixes the problem. > > arrgh! u kidding .. me .. ok .. thanks for the heads up! - a. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Connection Errors
On Tue, 6 May 2008, swejis wrote: > > OK, were back in business. > > Built and installed the debug-initiator. > > The [scsi_eh_xx] scsi_wq_xx] processes, there are about 60 of those > before I have even started open-iscsi, zombies ? > Eh. I do not know what is on your box. If you have not started open-iscsi they could be from something else. > May 6 21:03:53 manjula iscsid: connection3:0 is operational now > May 6 21:03:53 manjula iscsid: connection4:0 is operational now > > 3 and 4 now, could this be caused by those processes ? > I am not sure what you are doing. If yo had started iscsi previously then the session number would be incremented like it is above. > I would have expected this version to be very noisy log-wise, however It should be really noisy. Did you build with "make DEBUG_SCSI=1"? > I have stressed the disk quite alot now and have not seen anything in > the log. Performance actually also looks better. 3GB in 40 sec, that > is far better than before. > > Those processes, could I just shut everything down and kill the > remaining ? > Yeah, reboot the box, use the new modules and tools build with DEBUG_SCSI=1. Remove the suse tools, stop the init iscsi and open-iscsi init scripts from running, and then just start iscsid by hand. Then run iscsiadm by hand. > Rgds > Jonas > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Bug 197136 in Gentoo
On May 5, 6:05 pm, aspasia <[EMAIL PROTECTED]> wrote: > Hello again, > > Also trying to configure iscsi root on a Gentoo build server; I > followed instructions to configure the initiator: > > http://gentoo-wiki.com/HOWTO_iscsi > > But as I attempt to emerge, I encountered an installation error: > . > * Preparing iscsi_tcp module > make: *** No rule to make target `linux_2_6_24', needed by > `kernel_check'. Stop. > * > * ERROR: sys-block/open-iscsi-2.0.865.12 failed. > * Call stack: > * ebuild.sh, line 49: Called src_compile > * environment, line 3462: Called linux-mod_src_compile > * environment, line 2638: Called die > > > Upon googling I stumbled across this bug: > > http://bugs.gentoo.org/show_bug.cgi?id=197136 > > My question: Is there a workaround to this - and if so, is there some > instructions that documents how to workaround this bug? I'd like to > configure my gentoo host as an initiator. The work around that I have been using is to compile open-iscsi from the source tarball and then copy the iscsid init file from portage ( / usr/portage/sys-block/openiscsi/files/iscsid-init.d to /etc/init.d/ iscsid) and edit it to correct the paths a bit: #7c7 #< CONFIG_FILE=/etc/iscsid.conf #--- #> CONFIG_FILE=/etc/iscsi/iscsid.conf #11,12c11,12 #< INITIATORNAME=/etc/initiatorname.iscsi #< DAEMON=/usr/sbin/iscsid #--- #> INITIATORNAME=/etc/iscsi/initiatorname.iscsi #> DAEMON=/sbin/iscsid > thanks in advance, > > A. Let me know how and if this works out for you, Shaun --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Bug 197136 in Gentoo
I since I am not familiar with traversing the labyrinth of "Gentoo'ism" ... (at least for now,) ... I downloaded the open-iscsi-ebuild tarball, place into a /usr/local/portage/sys-block/open-iscsi directory and followed the steps on How to Install 3rdParty ebduild: http://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds It actually worked for me .. I got it to install, and now am in the process of configuring for iscsiroot ... crossing my fingers, hoping it would work. - a. > The work around that I have been using is to compile open-iscsi from > the source tarball and then copy the iscsid init file from portage ( / > usr/portage/sys-block/openiscsi/files/iscsid-init.d to /etc/init.d/ > iscsid) and edit it to correct the paths a bit: > > #7c7 > #< CONFIG_FILE=/etc/iscsid.conf > #--- > #> CONFIG_FILE=/etc/iscsi/iscsid.conf > #11,12c11,12 > #< INITIATORNAME=/etc/initiatorname.iscsi > #< DAEMON=/usr/sbin/iscsid > #--- > #> INITIATORNAME=/etc/iscsi/initiatorname.iscsi > #> DAEMON=/sbin/iscsid > > > thanks in advance, > > > > A. > > Let me know how and if this works out for you, > > Shaun > > > > > -- A S P A S I A . . . . . . . . . . .. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
open-iscsi vs. initiator-tools ... in Gentoo
Hello all, I am just curious, I installed the open-iscsi (emerge sys-block/open- iscsi) various iscsi binaries are installed: r04s23 scsi # iscsiadm -V iscsiadm version 2.0-868 r04s23 scsi # iscsistart -v iscsistart version 2.0-868 r04s23 scsi # seems like it's ok ... then I try to start the daemon - /etc/init.d/ iscsi start and it seems like unlike other distros a startup script was not automatically created i did which: which iscsid /usr/sbin/iscsid r04s23 scsi # The binary seems to be there ... running it does not seem to work - and I did not see any of the modules installed ... So I emerged search and noticed the following: emerge --search iscsi Searching... [ Results for search key : iscsi ] [ Applications found : 3 ] * sys-block/iscsi-initiator-core-tools [ Masked ] Latest version available: 2.3 Latest version installed: [ Not Installed ] Size of files: 50 kB Homepage: http://iscsi-initiator-core.org/ Description: iscsi-initiator-core is a full featured iSCSI Initiator stack. License: GPL-2 * sys-block/iscsitarget Latest version available: 0.4.15-r1 Latest version installed: [ Not Installed ] Size of files: 100 kB Homepage: http://iscsitarget.sourceforge.net/ Description: Open Source iSCSI target with professional features License: GPL-2 * sys-block/open-iscsi Latest version available: 2.0.868_rc1 Latest version installed: 2.0.868_rc1 Size of files: 269 kB Homepage: http://www.open-iscsi.org/ Description: Open-iSCSI is a high performance, transport independent, multi-platform implementation of RFC3720 License: GPL-2 . seems like the initiator-tools is not installed - so what is the difference between the initiator-tools and open-iscsi? I thought the latter is a superset? Finally, wouldn't the installation of these automatically also include the necessary modules? I do not see them in the usual /lib/modules/ //drivers/scsi ?? thanks in advance, Aspasia Please advise. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: open-iscsi vs. initiator-tools ... in Gentoo
2008/5/6 aspasia <[EMAIL PROTECTED]>: > then I try to start the daemon - /etc/init.d/ > iscsi start and it seems like unlike other distros a startup script > was not automatically created i did which: Don't you mean /etc/init.d/iscsid ? > which iscsid > /usr/sbin/iscsid > r04s23 scsi # > > The binary seems to be there ... running it does not seem to work - > and I did not see any of the modules installed ... > So I emerged search and noticed the following: > > emerge --search iscsi > Searching... > [ Results for search key : iscsi ] > [ Applications found : 3 ] > > * sys-block/iscsi-initiator-core-tools [ Masked ] > Latest version available: 2.3 > Latest version installed: [ Not Installed ] > Size of files: 50 kB > Homepage: http://iscsi-initiator-core.org/ > Description: iscsi-initiator-core is a full featured iSCSI > Initiator stack. > License: GPL-2 > > * sys-block/iscsitarget > Latest version available: 0.4.15-r1 > Latest version installed: [ Not Installed ] > Size of files: 100 kB > Homepage: http://iscsitarget.sourceforge.net/ > Description: Open Source iSCSI target with professional > features > License: GPL-2 > > * sys-block/open-iscsi > Latest version available: 2.0.868_rc1 > Latest version installed: 2.0.868_rc1 > Size of files: 269 kB > Homepage: http://www.open-iscsi.org/ > Description: Open-iSCSI is a high performance, transport > independent, multi-platform implementation of RFC3720 > License: GPL-2 > > . > > seems like the initiator-tools is not installed - so what is the > difference between the initiator-tools and open-iscsi? I thought > the latter is a superset? > > Finally, wouldn't the installation of these automatically also include > the necessary modules? I do not see them in the usual /lib/modules/ > //drivers/scsi ?? > > thanks in advance, > > Aspasia > > Please advise. > -- Shaun --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: open-iscsi vs. initiator-tools ... in Gentoo
> Don't you mean /etc/init.d/iscsid ? YES! ... sorry ... yes, /etc/init.d/iscsid or (in other flavors the script is - /etc/rc.d/open-iscsi) ... does not seem to exist. I also noticed the iscsi modules have not been installed. Do I need to install the initiator-tools also? - a. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: open-iscsi vs. initiator-tools ... in Gentoo
2008/5/6 a s p a s i a <[EMAIL PROTECTED]>: > > > Don't you mean /etc/init.d/iscsid ? > > YES! ... sorry ... > > yes, /etc/init.d/iscsid or (in other flavors the script is - > /etc/rc.d/open-iscsi) ... does not seem to exist. I'm not sure how or where you got this alternative ebuild from but you can install the init.d file as per my other emails. > I also noticed the iscsi modules have not been installed. > Do I need to install the initiator-tools also? No. At least, I don't have them installed and it is working. > - a. > > > > > > -- Shaun --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: open-iscsi vs. initiator-tools ... in Gentoo
Hello Shaun and all, On Tue, May 6, 2008 at 2:31 PM, Shaun Meyer <[EMAIL PROTECTED]> wrote: > 1. I downloaded the tarball and compiled from temp. 2. I copied the initd.debian sample startup script into the /etc/init.d/open-iscsi (is what I called it) and ensured it's chmod'ed to +x 3. Ensured to edit the script to fit my environment: (paths, the /etc/init.d/functions.sh, etc.) 4. I still had issues in starting the daemon or even connecting to a disk; with debugging turned on, I noticed the following error: iscsistart: initiator reported error (9 - internal error) Which the /var/log/messages explicitly informed me that: May 6 08:50:30 localhost session4: couldn't create a new connection.<6>scsi12 : iSCSI Initiator over TCP/IP May 6 08:50:30 localhost connection5:0: Could not create connection due to crc32c loading error. Make sure the crc32c module is built as a module or into the kernel 5. I know I did load the crc32c module in my make menuconfig, HOWEVER, I did not update the automodules file, so I did the following (for future reboots): echo "crc32c" >> /etc/modules.autoload.d/kernel-2.6 and also just did a modprobe -q crc32c 6. Upon re-starting the iscsiadm command, I was able to login and connect to disk! thanks a lot! - a. -- A S P A S I A . . . . . . . . . . .. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: IPv4/IPv6 initiator-target--automatic mapping of targets
Hello Mike, Let me explain the sequence of events -- The system reboots -- Open iscsi is enabled at start up Issue 1 ==>> From the database, the initiator logins twice to the same target via TWO TCP connections which are established on IPv4 and IPv6 sockets. Yes, if i disable automatic node startup, then it is fine, I can login to the target via specific portal by using iscsiadm comamands. But problem is when it configured for automatic login. As said earlier, I am looking for a solution at iSCSI layer. ==>> for the second issue, I searched further but still need your help . Yes, I find an entry under /dev/disk/by-id as say " scsi-149455400123456" ? Here is where I am not able to get you how to make it consistent. 1. mount /dev/disk/by-id/scsi-XXX /mnt/iscsi 2. output of mount /dev/sdd on /mnt/iscsi type ext3 (rw) 3. Created fstab entry /dev/sdd /mnt/iscsi auto _netdev 0 0 4. Reboot fstab retains the entry, but the mount output does not have it. When it logged in this time, it has different sd. I am not using udev rules. Once again, thanks for your time and suggestions. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
