Help:insmod: error inserting ib_iser.ko

[DeepBlue]

There is a error with I inserting the ib_iser.ko module as following:
====================================================
[root@localhost init.d]# insmod /lib/modules/2.6.18-8.el5/kernel/
drivers/infiniband/ulp/iser/ib_iser.ko
insmod: error inserting '/lib/modules/2.6.18-8.el5/kernel/drivers/
infiniband/ulp/iser/ib_iser.ko': -1 Unknown symbol in module
====================================================
my linux kernel 2.6.18-8.el5
who can help me?

[Erez Zilber]

This is because your ib_iser module was built against open-iscsi from
the redhat kernel (2.6.18-8.el5). You are currently running open-iscsi
modules that you took from open-iscsi.org. If you run 'dmesg -c',
you'll see the list of symbols that it disagrees on.

What can you do? Assuming that you want to use iSER, use the
open-iscsi kernel modules from kernel + open-iscsi userspace tools
from open-iscsi.org. Another (easier) option is to install OFED that
has open-iscsi with iSER support.

Erez

[Xintao Zhang]

I don't want use th "iser"

I want the open-iscsi run normally run,can you  help me?

2009/12/16 Erez Zilber <erezz...@gmail.com>

--

You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To post to this group, send email to open-...@googlegroups.com.
To unsubscribe from this group, send email to open-iscsi+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.

[Erez Zilber]

I guess that you want to run open-iscsi over iscsi_tcp which is the
default open-iscsi transport. Assuming that all other modules were
loaded successfully (libiscsi, iscsi_tcp, scsi_transport_iscsi and
libiscsi_tcp (depends on the version of open-iscsi that you use)), you
don't need to do anything. open-iscsi has multiple transport
(iscsi_tcp, ib_iser, bnx2i, cxgb3i). The error that you got means that
the ib_iser transport could not be loaded, but you don't need iSER
anyway.

Erez

[Xintao Zhang]

Thanks Erez

2009/12/16 Erez Zilber <erezz...@gmail.com>

[Xintao Zhang]

I start open-iscsi with you method,but appear a problem.

I use the tail -f /var/log/messages can't find iscis device.

can you help me?

2009/12/17 Xintao Zhang <zhangxin...@gmail.com>

[Erez Zilber]

Please do the following:
1. Stop open-iscsi: make sure that 'lsmod | grep iscsi' & 'ps aux |
grep iscsi' return nothing.
2. Make sure that no other version of open-iscsi is installed: run
'rpm -qa | grep iscsi'.
2. Run 'dmesg -c'.
3. Start open-iscsi: /etc/init.d/open-iscsi start
4. Send the output of 'lsmod | grep iscsi' & 'dmesg -c'.

Erez

On Thu, Dec 17, 2009 at 4:23 AM, Xintao Zhang

[Xintao Zhang]

Hi Erez

I do it with you method,I can see the target disk.

I want know what tools I can use if I use the ib_iSER module or I don't want see the error prompt in the screen.

Do you have good idae ?

2009/12/20 Erez Zilber <erezz...@gmail.com>

[Xintao Zhang]

Hi Erez

I can see the target disk in dmesg -c,but where is not device in /dev/

can you  can help me ?

2009/12/21 Xintao Zhang <zhangxin...@gmail.com>

[Erez Zilber]

You shouldn't care too much about the ib_iser error message. If you
don't want to see it, edit /etc/init.d/open-iscsi and remove the
modprobe line that loads ib_iser.

Erez

On Mon, Dec 21, 2009 at 10:19 AM, Xintao Zhang

[Erez Zilber]

What is the output of 'iscsiadm -m session -P 3'? You should see something like:

************************
Attached SCSI devices:
************************
Host Number: 29 State: running
scsi29 Channel 00 Id 0 Lun: 0
Attached scsi disk sdb State: running

If you have a session without an attached device, maybe your iSCSI
target exposes a target (e.g. iqn.something) but there is no device
attached to that target. Which target do you use?

Erez

On Mon, Dec 21, 2009 at 10:31 AM, Xintao Zhang

[Xintao Zhang]

Hi Erez

I use iscsitarget-1.4.19 in another pc.

In Windows xp I can use microsoft initiator operate the target in full feature.

there is a screen print as following:

=====================================

csi1 : iSCSI Initiator over TCP/IP
  Vendor: IET       Model: VIRTUAL-DISK      Rev: 0  
  Type:   Direct-Access                      ANSI SCSI revision: 04
SCSI device sdb: 12000001 512-byte hdwr sectors (6144 MB)
sdb: Write Protect is off
sdb: Mode Sense: 77 00 00 08
SCSI device sdb: drive cache: write through
SCSI device sdb: 12000001 512-byte hdwr sectors (6144 MB)
sdb: Write Protect is off
sdb: Mode Sense: 77 00 00 08
SCSI device sdb: drive cache: write through
 sdb: sdb1
sd 1:0:0:0: Attached scsi disk sdb
sd 1:0:0:0: Attached scsi generic sg1 type 0
Loading iSCSI transport class v2.0-870.
iscsi: registered transport (tcp)

[root@localhost open-iscsi-2.0-870.3]# iscsiadm -m session -P 3
iSCSI Transport Class version 2.0-870
iscsiadm version 2.0-870
iscsiadm: No active sessions.
===============================

How to solve this problem?

 

                               ZHANGXINTAO

2009/12/21 Erez Zilber <erezz...@gmail.com>

[Mike Christie]

On 12/22/2009 01:21 AM, Xintao Zhang wrote:
> Hi Erez
> I use iscsitarget-1.4.19 in another pc.
> In Windows xp I can use microsoft initiator operate the target in full
> feature.
> there is a screen print as following:
> =====================================
> csi1 : iSCSI Initiator over TCP/IP
> Vendor: IET Model: VIRTUAL-DISK Rev: 0
> Type: Direct-Access ANSI SCSI revision: 04
> SCSI device sdb: 12000001 512-byte hdwr sectors (6144 MB)
> sdb: Write Protect is off
> sdb: Mode Sense: 77 00 00 08

I do not think that is normal with iet, but it looks like everything
goes ok below.

> SCSI device sdb: drive cache: write through
> SCSI device sdb: 12000001 512-byte hdwr sectors (6144 MB)
> sdb: Write Protect is off
> sdb: Mode Sense: 77 00 00 08
> SCSI device sdb: drive cache: write through
> sdb: sdb1
> sd 1:0:0:0: Attached scsi disk sdb

Do you see sdb in /sys/block/sdb?

Do you see anything in /dev/disk/ ?