no iscsiadm came with Centos
iscsi
I have iscsid and iscsi.conf on my centos Linux, but there is no iscsiadm.
should I compile the source code and copy it ?
also , I couldn't find any sample command related to chap.
Thanks
H. "Miz" Jones
Bigadmin
still
no iscsiadm, so downloaded newest version of open-iscsi to compile,
but got
kernel version error ( we are using Centos 4 which the kernel version
is 2.6.9 ).
upgraded two of our servers ( now our kernel version is 2.6.28-8 ),
downloaded open-iscsi, ran make and then make install
now I have iscsiadm, was happy for a while, but now I am getting
following error
when I am trying to start open-iscsi
would you please let me know what will be the solution .
Starting iSCSI initiator service: FATAL: Error inserting ib_iser (/lib/
modules/2.6.18-8.el5/kernel/drivers/infiniband/ulp/iser/ib_iser.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
and dmesg shows :
Loading iSCSI transport class v2.0-865.
iscsi: registered transport (tcp)
ib_iser: disagrees about version of symbol iscsi_conn_setup
ib_iser: Unknown symbol iscsi_conn_setup
ib_iser: disagrees about version of symbol iscsi_verify_itt
ib_iser: Unknown symbol iscsi_verify_itt
ib_iser: disagrees about version of symbol
iscsi_session_recovery_timedout
ib_iser: Unknown symbol iscsi_session_recovery_timedout
ib_iser: disagrees about version of symbol iscsi_conn_bind
ib_iser: Unknown symbol iscsi_conn_bind
ib_iser: disagrees about version of symbol iscsi_session_setup
ib_iser: Unknown symbol iscsi_session_setup
ib_iser: disagrees about version of symbol class_to_transport_session
ib_iser: Unknown symbol class_to_transport_session
ib_iser: disagrees about version of symbol iscsi_conn_failure
ib_iser: Unknown symbol iscsi_conn_failure
ib_iser: disagrees about version of symbol iscsi_complete_pdu
ib_iser: Unknown symbol iscsi_complete_pdu
ib_iser: disagrees about version of symbol iscsi_register_transport
ib_iser: Unknown symbol iscsi_register_transport
ib_iser: disagrees about version of symbol iscsi_set_param
ib_iser: Unknown symbol iscsi_set_param
Bigadmin
2.6.18-8.el5
Mike Christie
> the strange thing is iscsi-initiator-utils was already installed , but
> still
> no iscsiadm, so downloaded newest version of open-iscsi to compile,
> but got
You are using centos 4, right? The version of iscsi-initiator-utils in
Centos 4 has linux-iscsi which is a different project. That project does
not have iscsiadm.
In Centos 5, the iscsi-initiator-utils package has open-iscsi which as
you know has iscsiadm.
You are using the open-iscsi.org modules with the RHEL5/Centos kernel.
The open-iscsi.org modules are different and so the iser modules that
come with RHEL5/Centos cannot be used with the open-iscsi.org modules.
If you are not using iser, those messages can be ignored.
Bigadmin
get
any error , just following warning
Setting up iSCSI targets: iscsiadm: No records found!
I ran following commands:
/sbin/iscsiadm --mode discovery --type sendtargets --portal
10.10.10.13:3260
/sbin/iscsiadm --mode node --targetname my_target_name --portal
10.10.10.13:3260
but when I want to login , I get the following error:
/sbin/iscsiadm -m node --targetname=my_Target_Name --
portal=10.10.10.13:3260 --interface=iface0 --login
Login session [iface: iface0, target: my_Target_Name, portal:
10.10.10.13,3260]
iscsiadm: initiator reported error (4 - encountered connection
failure)
iscsiadm: Could not execute operation on all records. Err 107.
when I try to start iscsid with debug option I get following error:
iscsid: Missing or Invalid version from /sys/module/
scsi_transport_iscsi/version. Make sure a up to date
scsi_transport_iscsi module is loaded and a up todate version of
iscsid is running. Exiting...
how come there is no /sys/module/scsi_transport_iscsi/version !!!!!
Thanks
Bigadmin
when I start /sbin/iscsid -d 8 -f &
iscsid: Missing or Invalid version from /sys/module/
scsi_transport_iscsi/version. Make sure a up to date
scsi_transport_iscsi module is loaded and a up todate version of
iscsid is running. Exiting...
also now that I am checking, following directories are not created at
compile time:
/sys/module/scsi_transport_iscsi/
/sys/module/iscsi_tcp/
/sys/module/libiscsi
I think compiling open-iscsi suppose to create those direcotries but
it didn't.
sudo /sbin/modinfo iscsi_tcp
filename: /lib/modules/2.6.18-8.el5/kernel/drivers/scsi/
iscsi_tcp.ko
license: GPL
description: iSCSI/TCP data-path
author: Dmitry Yusupov <dmitr...@yahoo.com>, Alex Aizman
<itn...@yahoo.com>
srcversion: 694762975927EBB1F70B098
depends: libiscsi,libiscsi,scsi_transport_iscsi,scsi_mod
vermagic: 2.6.18-8.el5 SMP mod_unload 686 REGPARM 4KSTACKS
gcc-4.1
parm: max_lun:uint
sudo /sbin/modinfo scsi_transport_iscsi
filename: /lib/modules/2.6.18-8.el5/kernel/drivers/scsi/
scsi_transport_iscsi.ko
version: 2.0-865
license: GPL
description: iSCSI Transport Interface
author: Mike Christie <mich...@cs.wisc.edu>, Dmitry Yusupov
<dmitr...@yahoo.com>, Alex Aizman <itn...@yahoo.com>
srcversion: 1F4E00869D7A3F6686A8237
depends: scsi_mod
vermagic: 2.6.18-8.el5 SMP mod_unload 686 REGPARM 4KSTACKS
gcc-4.1
On Sep 4, 12:12 pm, Bigadmin <is...@unixplanet.biz> wrote:
> removed the "modprobe -q ib_iser" from open-iscsi, and now i don't
> get
> any error , just following warning
> Setting up iSCSI targets: iscsiadm: No records found!
>
> I ran following commands:
> /sbin/iscsiadm --mode discovery --type sendtargets --portal
> 10.10.10.13:3260
> /sbin/iscsiadm --mode node --targetname my_target_name --portal
> 10.10.10.13:3260
>
> but when I want to login , I get the following error:
> /sbin/iscsiadm -m node --targetname=my_Target_Name --
> portal=10.10.10.13:3260 --interface=iface0 --login
> Login session [iface: iface0, target: my_Target_Name, portal:
> 10.10.10.13,3260]
> iscsiadm: initiator reported error (4 - encountered connection
> failure)
> iscsiadm: Could not execute operation on all records. Err 107.
>
> when I try to start iscsid with debug option I get following error:
> iscsid: Missing or Invalidversionfrom /sys/module/
> scsi_transport_iscsi/version. Make sure a up to date
> scsi_transport_iscsi module is loaded and a up todateversionof
> iscsid is running. Exiting...
>
> how come there is no /sys/module/scsi_transport_iscsi/version!!!!!
>
> Thanks
>
> On Aug 31, 5:52 pm, Mike Christie <micha...@cs.wisc.edu> wrote:
>
> > Bigadmin wrote:
> > > the strange thing is iscsi-initiator-utils was already installed , but
> > > still
> > > no iscsiadm, so downloaded newestversionof open-iscsi to compile,
> > > but got
>
> > You are using centos 4, right? Theversionof iscsi-initiator-utils in
> > Centos 4 has linux-iscsi which is a different project. That project does
> > not have iscsiadm.
>
> > In Centos 5, the iscsi-initiator-utils package has open-iscsi which as
> > you know has iscsiadm.
>
> > > kernelversionerror ( we are using Centos 4 which the kernelversion
> > > is 2.6.9 ).
>
> > > upgraded two of our servers ( now our kernelversionis 2.6.28-8 ),
> > > downloaded open-iscsi, ran make and then make install
> > > now I have iscsiadm, was happy for a while, but now I am getting
> > > following error
> > > when I am trying to start open-iscsi
>
> > > would you please let me know what will be the solution .
>
> > > Starting iSCSI initiator service: FATAL: Error inserting ib_iser (/lib/
> > > modules/2.6.18-8.el5/kernel/drivers/infiniband/ulp/iser/ib_iser.ko):
> > > Unknown symbol in module, or unknown parameter (see dmesg)
>
> > > and dmesg shows :
>
> > > Loading iSCSI transport class v2.0-865.
> > > iscsi: registered transport (tcp)
> > > ib_iser: disagrees aboutversionof symbol iscsi_conn_setup
> > > ib_iser: Unknown symbol iscsi_conn_setup
> > > ib_iser: disagrees aboutversionof symbol iscsi_verify_itt
> > > ib_iser: Unknown symbol iscsi_verify_itt
> > > ib_iser: disagrees aboutversionof symbol
> > > iscsi_session_recovery_timedout
> > > ib_iser: Unknown symbol iscsi_session_recovery_timedout
> > > ib_iser: disagrees aboutversionof symbol iscsi_conn_bind
> > > ib_iser: Unknown symbol iscsi_conn_bind
> > > ib_iser: disagrees aboutversionof symbol iscsi_session_setup
> > > ib_iser: Unknown symbol iscsi_session_setup
> > > ib_iser: disagrees aboutversionof symbol class_to_transport_session
> > > ib_iser: Unknown symbol class_to_transport_session
> > > ib_iser: disagrees aboutversionof symbol iscsi_conn_failure
> > > ib_iser: Unknown symbol iscsi_conn_failure
> > > ib_iser: disagrees aboutversionof symbol iscsi_complete_pdu
> > > ib_iser: Unknown symbol iscsi_complete_pdu
> > > ib_iser: disagrees aboutversionof symbol iscsi_register_transport
> > > ib_iser: Unknown symbol iscsi_register_transport
> > > ib_iser: disagrees aboutversionof symbol iscsi_set_param
iscsi
or when I do modprobe. so I did modprobe iscsi_tcp and then started
iscsid with debugging option, here is the output.
it can not bind to eth0:0
any idea why I have this problem.
Thanks
sudo /sbin/service open-iscsi start
Starting iSCSI initiator service: [ OK ]
Setting up iSCSI targets: Login session [iface: iface0, target:
C1P0.171, portal: 10.10.10.12,3260]
iscsiadm: initiator reported error (4 - encountered connection failure)
iscsiadm: Could not log into all portals. Err 107.
[ OK ]
iscsid: Found hardware address 00:14:22:18:72:4c
iscsid: Matches 00:14:22:18:72:4C to eth0
iscsid: Binding session 0 to eth0:0
iscsid: Could not bind connection 0 to eth0:0
iscsid: cannot make a connection to 10.10.10.12:3260 (19)
iscsid: thread 0936f0a0 delete: state 0
iscsid: deleting a scheduled/waiting thread!
iscsid: destroying session
Bigadmin
the code in open-iscsi does not have the latest patch.
open-iscsi.org iscsiadm still writing node config files in /etc/iscsi/
nodes
rather than /var/lib/iscsi/node.
> > author: Dmitry Yusupov <dmitry_...@yahoo.com>, Alex Aizman
> > <itn...@yahoo.com>
> > srcversion: 694762975927EBB1F70B098
> > depends: libiscsi,libiscsi,scsi_transport_iscsi,scsi_mod
> > vermagic: 2.6.18-8.el5 SMP mod_unload 686 REGPARM 4KSTACKS
> > gcc-4.1
> > parm: max_lun:uint
>
> > sudo /sbin/modinfo scsi_transport_iscsi
> > filename: /lib/modules/2.6.18-8.el5/kernel/drivers/scsi/
> > scsi_transport_iscsi.ko
> > version: 2.0-865
> > license: GPL
> > description: iSCSI Transport Interface
> > author: Mike Christie <micha...@cs.wisc.edu>, Dmitry Yusupov
> > <dmitry_...@yahoo.com>, Alex Aizman <itn...@yahoo.com>
Mike Christie
> my bad, those directories show up when open-iscsi starts,
> or when I do modprobe. so I did modprobe iscsi_tcp and then started
> iscsid with debugging option, here is the output.
> it can not bind to eth0:0
>
> any idea why I have this problem.
>
> Thanks
>
> sudo /sbin/service open-iscsi start
> Starting iSCSI initiator service: [ OK ]
> Setting up iSCSI targets: Login session [iface: iface0, target:
> C1P0.171, portal: 10.10.10.12,3260]
> iscsiadm: initiator reported error (4 - encountered connection failure)
> iscsiadm: Could not log into all portals. Err 107.
> [ OK ]
>
> iscsid: Found hardware address 00:14:22:18:72:4c
> iscsid: Matches 00:14:22:18:72:4C to eth0
> iscsid: Binding session 0 to eth0:0
> iscsid: Could not bind connection 0 to eth0:0
>
Can you do
ping -I eth0:0 10.10.10.12
Mike Christie
> I have connected to target,
> the code in open-iscsi does not have the latest patch.
> open-iscsi.org iscsiadm still writing node config files in /etc/iscsi/
> nodes
> rather than /var/lib/iscsi/node.
>
Just so you know there is no patch for open-iscsi.org to put config
files in /var/lib/iscsi instead of /etc/iscsi. FC/RHEL does it and I
think SUSE does, but for upstream we have not done it since we still
need a script to migrate users or some compat code for users of /etc/iscsi.
iscsi
I am connected to Targets and mounted the seen hard drives.
started to test with copying a large number of files, but hard drives
were dettached
after a while.
following lines are coming up in log files right after I start copy files:
would you please let me know what do you think.
Sep 6 09:12:29 Anaconda kernel: iscsi_tcp: dropping R2T itt 75 in
recovery...
Sep 6 09:12:29 Anaconda kernel: iscsi_tcp: dropping R2T itt 116 in
recovery...
Sep 6 09:14:09 Anaconda kernel: iscsi_tcp: dropping R2T itt 34 in
recovery...
Sep 6 09:14:09 Anaconda kernel: iscsi_tcp: dropping R2T itt 72 in
recovery...
Sep 6 09:14:09 Anaconda kernel: iscsi_tcp: dropping R2T itt 19 in
recovery...
Sep 6 09:14:09 Anaconda kernel: iscsi_tcp: dropping R2T itt 116 in
recovery...
Sep 6 09:14:09 Anaconda kernel: iscsi_tcp: dropping R2T itt 10 in
recovery...
Sep 6 09:14:09 Anaconda kernel: iscsi_tcp: dropping R2T itt 21 in
recovery...
Sep 6 09:14:09 Anaconda kernel: iscsi_tcp: dropping R2T itt 12 in
recovery...
Sep 6 09:14:09 Anaconda kernel: iscsi_tcp: dropping R2T itt 25 in
recovery...
Sep 6 09:14:56 Anaconda kernel: sd 5:0:0:3: SCSI error: return code =
0x00010000
Sep 6 09:14:56 Anaconda kernel: sd 5:0:0:3: SCSI error: return code =
0x00010000
Sep 6 09:14:56 Anaconda kernel: sd 5:0:0:3: SCSI error: return code =
0x00010000
Sep 6 09:14:56 Anaconda kernel: sd 5:0:0:3: SCSI error: return code =
0x00010000
Sep 6 09:14:56 Anaconda kernel: sd 5:0:0:3: SCSI error: return code =
0x00010000
Sep 6 09:14:56 Anaconda kernel: sd 5:0:0:3: SCSI error: return code =
0x00010000
Sep 6 09:14:56 Anaconda kernel: sd 5:0:0:3: SCSI error: return code =
0x00010000
Sep 6 09:14:56 Anaconda kernel: sd 5:0:0:3: SCSI error: return code =
0x00010000
Sep 6 09:14:56 Anaconda kernel: sd 5:0:0:3: SCSI error: return code =
0x00010000
Sep 6 09:14:56 Anaconda kernel: sd 5:0:0:3: SCSI error: return code =
0x00010000
Sep 6 09:14:56 Anaconda kernel: sd 5:0:0:3: SCSI error: return code =
0x00010000
Sep 6 09:14:56 Anaconda kernel: sd 5:0:0:3: SCSI error: return code =
0x00010000
Sep 6 09:14:56 Anaconda kernel: sd 5:0:0:3: SCSI error: return code =
0x00010000
Sep 6 09:14:56 Anaconda kernel: sd 5:0:0:3: SCSI error: return code =
0x00010000
Sep 6 09:14:56 Anaconda kernel: sd 5:0:0:3: SCSI error: return code =
0x00010000
Mike Christie
> Thank you Mike,
>
> I am connected to Targets and mounted the seen hard drives.
> started to test with copying a large number of files, but hard drives
> were dettached
> after a while.
>
> following lines are coming up in log files right after I start copy files:
> would you please let me know what do you think.
>
I forgot, are you using a open-iscsi.org release (modules and tools), or
are you using a centos kernel and its iscsi modules and are you using
Cento's iscsi-initiator-utils rpm?
there should also be more to the log. Something about a connection error
or failure or nop timing out. Could you send all of the log? And what
target were you using again?
It looks like the session is getting dropped while IO is running. And
then we cannot log back in or the IO keeps timing out. If you could run
"iscsiadm -m session -P 3". If that does not work run "iscsiadm -m
session -i".
iscsi
I was going to use open-iscsi.org modules and iscsiadm, but it didn't
work for me, don't know why
then did yum install iscsi-initiator-utils-6.2.0.742-0.6.el5 and it
worked with the same set of commands.
So practically it should be the modules that come with iscsi-initiator ,
but I am not sure if yum install will
update the .ko files as well ( I mean kernel modules ) . how do I know
which modules are built by who !!!!!
/sbin/modinfo iscsi_tcp
filename: /lib/modules/2.6.18-8.el5/kernel/drivers/scsi/iscsi_tcp.ko
license: GPL
description: iSCSI/TCP data-path
author: Dmitry Yusupov <dmitr...@yahoo.com>, Alex Aizman
<itn...@yahoo.com>
srcversion: 694762975927EBB1F70B098
depends: libiscsi,libiscsi,scsi_transport_iscsi,scsi_mod
vermagic: 2.6.18-8.el5 SMP mod_unload 686 REGPARM 4KSTACKS gcc-4.1
parm: max_lun:uint
/sbin/modinfo scsi_transport_iscsi
filename:
/lib/modules/2.6.18-8.el5/kernel/drivers/scsi/scsi_transport_iscsi.ko
version: 2.0-865
license: GPL
description: iSCSI Transport Interface
author: Mike Christie <mich...@cs.wisc.edu>, Dmitry Yusupov
<dmitr...@yahoo.com>, Alex Aizman <itn...@yahoo.com>
srcversion: 1F4E00869D7A3F6686A8237
depends: scsi_mod
vermagic: 2.6.18-8.el5 SMP mod_unload 686 REGPARM 4KSTACKS gcc-4.1
sudo /sbin/modinfo libiscsi
filename: /lib/modules/2.6.18-8.el5/kernel/drivers/scsi/libiscsi.ko
license: GPL
description: iSCSI library functions
author: Mike Christie
srcversion: A8372CAFBA5300E2EC522D7
depends: scsi_mod,scsi_transport_iscsi
vermagic: 2.6.18-8.el5 SMP mod_unload 686 REGPARM 4KSTACKS gcc-4.1
We are using iqstor target " http://iqstor.com/ " and here is the output
of iscsiadm -m session -i which shows
Negotiated parameters are different to those in /etc/iscsi/iscsi.conf
thats all the error i am seeing in /var/log/kern, a lot of R2T recovery
error, and then scsi error,
and when I restart the initiator and mount it , journal recovery.
sudo /sbin/iscsiadm -m session -p 3
iscsiadm: session mode: option '-p' is not allowed or supported
sudo /sbin/iscsiadm -m session -i
iscsiadm version 2.0-742
************************************
Session (sid 2) using module tcp:
************************************
TargetName: iQstor.C1P0.171
Portal Group Tag: 0
Network Portal: 10.10.10.12:3260
iSCSI Connection State: LOGGED IN
Internal iscsid Session State: NO CHANGE
************************
Negotiated iSCSI params:
************************
HeaderDigest: None
DataDigest: None
MaxRecvDataSegmentLength: 65536
MaxXmitDataSegmentLength: 1048576
FirstBurstLength: 0
MaxBurstLength: 1048576
ImmediateData: No
InitialR2T: Yes
MaxOutstandingR2T: 1
************************
Attached SCSI devices:
************************
Host Number: 9 State: running
scsi9 Channel 00 Id 0 Lun: 0
Attached scsi disk sdc State: running
scsi9 Channel 00 Id 0 Lun: 1
Attached scsi disk sdd State: running
scsi9 Channel 00 Id 0 Lun: 2
Attached scsi disk sde State: running
scsi9 Channel 00 Id 0 Lun: 3
Attached scsi disk sdf State: running
*********************************************************
********************************************************
less /var/lib/iscsi/nodes/iQstor.C1P0.171/10.10.10.12,3260
node.name = iQstor.C1P0.171
node.transport_name = tcp
node.tpgt = -1
node.active_conn = 1
node.startup = automatic
node.session.initial_cmdsn = 0
node.session.auth.authmethod = CHAP
node.session.auth.username =
node.session.auth.password =
node.session.timeo.replacement_timeout = 120
node.session.err_timeo.abort_timeout = 10
node.session.err_timeo.reset_timeout = 30
node.session.iscsi.InitialR2T = No
node.session.iscsi.ImmediateData = Yes
node.session.iscsi.FirstBurstLength = 262144
node.session.iscsi.MaxBurstLength = 16776192
node.session.iscsi.DefaultTime2Retain = 0
node.session.iscsi.DefaultTime2Wait = 0
node.session.iscsi.MaxConnections = 1
node.session.iscsi.MaxOutstandingR2T = 1
node.session.iscsi.ERL = 0
node.conn[0].address = 10.10.10.12
node.conn[0].port = 3260
node.conn[0].startup = manual
node.conn[0].tcp.window_size = 524288
node.conn[0].tcp.type_of_service = 0
node.conn[0].timeo.logout_timeout = 15
node.conn[0].timeo.login_timeout = 15
node.conn[0].timeo.auth_timeout = 45
node.conn[0].timeo.active_timeout = 5
node.conn[0].timeo.idle_timeout = 60
node.conn[0].timeo.ping_timeout = 5
node.conn[0].timeo.noop_out_interval = 10
node.conn[0].timeo.noop_out_timeout = 15
node.conn[0].iscsi.MaxRecvDataSegmentLength = 65536
node.conn[0].iscsi.HeaderDigest = None,CRC32C
node.conn[0].iscsi.DataDigest = None
node.conn[0].iscsi.IFMarker = No
node.conn[0].iscsi.OFMarker = No
****************************************************************************
Sep 6 15:12:02 Anaconda kernel: iscsi_tcp: dropping R2T itt 12 in
recovery...
Sep 6 15:12:02 Anaconda kernel: iscsi_tcp: dropping R2T itt 19 in
recovery...
Sep 6 15:12:02 Anaconda kernel: iscsi_tcp: dropping R2T itt 84 in
recovery...
Sep 6 15:12:02 Anaconda kernel: iscsi_tcp: dropping R2T itt 60 in
recovery...
Sep 6 15:12:02 Anaconda kernel: iscsi_tcp: dropping R2T itt 99 in
recovery...
Sep 6 15:12:02 Anaconda kernel: iscsi_tcp: dropping R2T itt 80 in
recovery...
Sep 6 15:12:02 Anaconda kernel: iscsi_tcp: dropping R2T itt 22 in
recovery...
Sep 6 15:12:02 Anaconda kernel: iscsi_tcp: dropping R2T itt 29 in
recovery...
Sep 6 15:12:02 Anaconda kernel: iscsi_tcp: dropping R2T itt 18 in
recovery...
Sep 6 15:12:02 Anaconda kernel: iscsi_tcp: dropping R2T itt 113 in
recovery...
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:13:15 Anaconda kernel: sd 7:0:0:3: SCSI error: return code =
0x00010000
Sep 6 15:35:47 Anaconda kernel: Loading iSCSI transport class v2.0-865.
Sep 6 15:35:48 Anaconda kernel: scsi8 : iSCSI Initiator over TCP/IP
Sep 6 15:35:49 Anaconda kernel: sdc: sdc1
Sep 6 15:35:49 Anaconda kernel: sdd: sdd1
Sep 6 15:35:49 Anaconda kernel: sde: sde1
Sep 6 15:35:49 Anaconda kernel: sdf: sdf1
Sep 6 15:35:51 Anaconda kernel: kjournald starting. Commit interval 5
seconds
Sep 6 15:35:51 Anaconda kernel: EXT3 FS on sdc1, internal journal
Sep 6 15:35:51 Anaconda kernel: EXT3-fs: recovery complete.
Sep 6 15:35:51 Anaconda kernel: EXT3-fs: mounted filesystem with
ordered data mode.
Sep 6 15:35:51 Anaconda kernel: kjournald starting. Commit interval 5
seconds
Sep 6 15:35:51 Anaconda kernel: EXT3 FS on sdd1, internal journal
Sep 6 15:35:51 Anaconda kernel: EXT3-fs: recovery complete.
Sep 6 15:35:51 Anaconda kernel: EXT3-fs: mounted filesystem with
ordered data mode.
Sep 6 15:35:51 Anaconda kernel: kjournald starting. Commit interval 5
seconds
Sep 6 15:35:51 Anaconda kernel: EXT3 FS on sde1, internal journal
Sep 6 15:35:51 Anaconda kernel: EXT3-fs: recovery complete.
Sep 6 15:35:51 Anaconda kernel: EXT3-fs: mounted filesystem with
ordered data mode.
Sep 6 15:35:52 Anaconda kernel: kjournald starting. Commit interval 5
seconds
:
iscsi
Removed iscsi that was installed from centos repository, and re-compiled
iscsi again.
so far so good, no error any more, just one connection error which I
think I can
ignore that one, because copying 99 GB with scp continues with no
problem so far.
( no interruption and no other errors in log files and speed varies
between 5MB to 13 MB )
Sep 10 11:02:51 Anaconda kernel: EXT3 FS on sdd1, internal journal
Sep 10 11:02:51 Anaconda kernel: EXT3-fs: mounted filesystem with
ordered data mode.
Sep 10 11:06:17 Anaconda kernel: connection1:0: iscsi: detected conn
error (1011)
Sep 10 11:15:26 Anaconda kernel: kjournald starting. Commit interval 5
seconds
Is there any 64 bit open-iscsi ? or can I use the same code on both 32
bit and 64 bit ?
Mike Christie
>
> Is there any 64 bit open-iscsi ? or can I use the same code on both 32
> bit and 64 bit ?
>
You cannot use the same code on 64 and 32 bit, unless you use a 32 bit
kernel and userspace tools on 64 bit archs and 32 bit archs.
If you use a 64 bit kernel you must compile the userspace parts of
open-iscsi as 64 bits. I think with most distros if you have 64 bit libs
installed, then when you run make this is done for you.
Bigadmin
My question was wrong, you are right, when we compile open-iscsi on 64
bit computer,
compiler should take care of generating 64 bit open-iscsi.
I should have asked if any one tested open-iscsi on 64 bit computer,
or
64 bit architecture is over seen in open-iscsi.
I have compiled open-iscsi on one of our 64 bit servers and so far I
didn't have any problem
however I have another question for you.
our iscsi enclosure comes with two controller each with two ports,
we should assign each LUN or virtual disk to one of the ports.
when we login to one portal ( target portal which will be one of
the ports on enclosure ) we will see all those LUNs or virtual hard
drives that are assigned to that port ( portal ) , but when the
controller
fails, LUNs on one portal will failover to other contorller with
different ip address
so we can not access to those LUNs or virtual disks with same ip
address.
we should rediscover the failedover portal, ( which this time has more
LUNs assigned to it
so fdisk -l will show more options with different device names ) and
mount the new
assigned hard drives. the reverse process should be done when the
failed port is
recovered ( so we should rediscover the portals again and remount
LUNs )
was wondering if there is any better solution for this problem , so
when
portal fails , our users can access the same set of virtual disks
through
different controller ( portal )
thanks
fail over will not affect user and when the port failed , our
initiator