QLogic QLE4062C - device-mapper: ioctl: error adding target to table
2351 views
Skip to first unread message
Joffer
May 29, 2008, 7:03:51 PM5/29/08
to open-iscsi
First of all, I appologise if this isn't the right place to post
QLogic HBA questions, but I saw others were doing it so I hope it's
ok.
My hardware:
Two QLogic iSCSI HBA QLE4062C (dual port) cards, each installed in a
Dell PE2950 server. Connected to a cisco gigabit switch (seperate
vlan) and a Dell EqualLogic PS5000XV iSCSI SAN. Each server has CentOS
5 x86_64 (v5.1 with latest updates installed).
I've (tried to) configured my servers for multipath iscsi shared
storage (will be a cluster setup when done). In my message log I get
these errors (first two lines aren't an error though):
qla4xxx 0000:09:01.1: DDB[2] MB0 4000 Tot 1 Next 0 State 0004 ConnErr
00000000 172.2x.yy.10:3260 "iqn.2001-05.com.equallogic:
0-8a0906-6accc8302-9ef00000a31483c2-ora-u02"
qla4xxx 0000:09:01.3: DDB[2] MB0 4000 Tot 1 Next 0 State 0004 ConnErr
00000000 172.2x.yy.10:3260 "iqn.2001-05.com.equallogic:
0-8a0906-6accc8302-9ef00000a31483c2-ora-u02"
device-mapper: table: 253:1: multipath: error getting device
device-mapper: ioctl: error adding target to table
qla4xxx: invalid ioctl magic number received.
qla4xxx: invalid ioctl magic number received.
qla4xxx: invalid ioctl magic number received.
qla4xxx: invalid ioctl magic number received.
I can see I've got some sort of "ioctl" problem, but that doesn't say
much to me :-/ Thats the reason I post here. The "funny" thing is that
it seems to work just fine though. I can read and write from one of
the servers (only mounted at one server). I just can't think these
'ioctl' errors should be normal.
What I've done so far is downloading the QLogic HBA driver, SANsurfer
and SANsurferCLI from QLogic website:
http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/SearchByProd.aspx?ProductCategory=82&Product=1037&ProductName=QLE4062C
SANsurfer Linux iSCSI Driver Installer (x86/x64) - v5.01.01.04-1
SANsurfer iscli (x86/x64) - v1.1.00.13
SANsurfer HBA Manager (x86/Intel 64) - v5.00.32
First I installed the driver using the driver-installer, and then both
SANsurfer utilities. I used the SANsurfer javaGUI to configure my
iSCSI target on both ports (for multipath) on both servers. After I
rebooted I got new devices from the iSCSI, /dev/sdc and /dev/sdd. Both
was the same volume. So I started to look into multipath, and here is
what my config looks like now:
/etc/multipath.conf:
<snip>
defaults {
user_friendly_names yes
udev_dir /dev
polling_interval 10
selector "round-robin 0"
path_grouping_policy multibus
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
prio_callout /bin/true
path_checker readsector0
rr_min_io 100
rr_weight priorities
failback immediate
no_path_retry fail
}
devnode_blacklist {
wwid 36001e4f02d38d4000f73ebab0546728f
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^hd[a-z][0-9]*"
devnode "^cciss!c[0-9]d[0-9]*[p[0-9]*]"
}
devices {
device {
vendor "EQLOGIC"
product "100E-00"
path_grouping_policy multibus
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
features "1 queue_if_no_path"
path_checker readsector0
}
}
</snip>
[root@linux02 ~]# multipath -l
mpath1 (36090a02830c8cc6ac28314a30000f09e) dm-0 EQLOGIC,100E-00
[size=250G][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][active]
\_ 3:0:1:0 sdc 8:32 [active][undef]
\_ 4:0:1:0 sdd 8:48 [active][undef]
I should mention I have not tried too much with the iscsi-initiator-
utils. I installed them, but never got the iscsiadm to list anything,
so I removed the package again.
/Christopher
QLogic HBA questions, but I saw others were doing it so I hope it's
ok.
My hardware:
Two QLogic iSCSI HBA QLE4062C (dual port) cards, each installed in a
Dell PE2950 server. Connected to a cisco gigabit switch (seperate
vlan) and a Dell EqualLogic PS5000XV iSCSI SAN. Each server has CentOS
5 x86_64 (v5.1 with latest updates installed).
I've (tried to) configured my servers for multipath iscsi shared
storage (will be a cluster setup when done). In my message log I get
these errors (first two lines aren't an error though):
qla4xxx 0000:09:01.1: DDB[2] MB0 4000 Tot 1 Next 0 State 0004 ConnErr
00000000 172.2x.yy.10:3260 "iqn.2001-05.com.equallogic:
0-8a0906-6accc8302-9ef00000a31483c2-ora-u02"
qla4xxx 0000:09:01.3: DDB[2] MB0 4000 Tot 1 Next 0 State 0004 ConnErr
00000000 172.2x.yy.10:3260 "iqn.2001-05.com.equallogic:
0-8a0906-6accc8302-9ef00000a31483c2-ora-u02"
device-mapper: table: 253:1: multipath: error getting device
device-mapper: ioctl: error adding target to table
qla4xxx: invalid ioctl magic number received.
qla4xxx: invalid ioctl magic number received.
qla4xxx: invalid ioctl magic number received.
qla4xxx: invalid ioctl magic number received.
I can see I've got some sort of "ioctl" problem, but that doesn't say
much to me :-/ Thats the reason I post here. The "funny" thing is that
it seems to work just fine though. I can read and write from one of
the servers (only mounted at one server). I just can't think these
'ioctl' errors should be normal.
What I've done so far is downloading the QLogic HBA driver, SANsurfer
and SANsurferCLI from QLogic website:
http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/SearchByProd.aspx?ProductCategory=82&Product=1037&ProductName=QLE4062C
SANsurfer Linux iSCSI Driver Installer (x86/x64) - v5.01.01.04-1
SANsurfer iscli (x86/x64) - v1.1.00.13
SANsurfer HBA Manager (x86/Intel 64) - v5.00.32
First I installed the driver using the driver-installer, and then both
SANsurfer utilities. I used the SANsurfer javaGUI to configure my
iSCSI target on both ports (for multipath) on both servers. After I
rebooted I got new devices from the iSCSI, /dev/sdc and /dev/sdd. Both
was the same volume. So I started to look into multipath, and here is
what my config looks like now:
/etc/multipath.conf:
<snip>
defaults {
user_friendly_names yes
udev_dir /dev
polling_interval 10
selector "round-robin 0"
path_grouping_policy multibus
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
prio_callout /bin/true
path_checker readsector0
rr_min_io 100
rr_weight priorities
failback immediate
no_path_retry fail
}
devnode_blacklist {
wwid 36001e4f02d38d4000f73ebab0546728f
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^hd[a-z][0-9]*"
devnode "^cciss!c[0-9]d[0-9]*[p[0-9]*]"
}
devices {
device {
vendor "EQLOGIC"
product "100E-00"
path_grouping_policy multibus
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
features "1 queue_if_no_path"
path_checker readsector0
}
}
</snip>
[root@linux02 ~]# multipath -l
mpath1 (36090a02830c8cc6ac28314a30000f09e) dm-0 EQLOGIC,100E-00
[size=250G][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][active]
\_ 3:0:1:0 sdc 8:32 [active][undef]
\_ 4:0:1:0 sdd 8:48 [active][undef]
I should mention I have not tried too much with the iscsi-initiator-
utils. I installed them, but never got the iscsiadm to list anything,
so I removed the package again.
/Christopher
Mike Christie
May 29, 2008, 10:03:40 PM5/29/08
to open-...@googlegroups.com, David Somayajulu
Joffer wrote:
> First of all, I appologise if this isn't the right place to post
> QLogic HBA questions, but I saw others were doing it so I hope it's
> ok.
>
> My hardware:
> Two QLogic iSCSI HBA QLE4062C (dual port) cards, each installed in a
> Dell PE2950 server. Connected to a cisco gigabit switch (seperate
> vlan) and a Dell EqualLogic PS5000XV iSCSI SAN. Each server has CentOS
> 5 x86_64 (v5.1 with latest updates installed).
>
> I've (tried to) configured my servers for multipath iscsi shared
> storage (will be a cluster setup when done). In my message log I get
> these errors (first two lines aren't an error though):
>
> qla4xxx 0000:09:01.1: DDB[2] MB0 4000 Tot 1 Next 0 State 0004 ConnErr
> 00000000 172.2x.yy.10:3260 "iqn.2001-05.com.equallogic:
> 0-8a0906-6accc8302-9ef00000a31483c2-ora-u02"
> qla4xxx 0000:09:01.3: DDB[2] MB0 4000 Tot 1 Next 0 State 0004 ConnErr
> 00000000 172.2x.yy.10:3260 "iqn.2001-05.com.equallogic:
> 0-8a0906-6accc8302-9ef00000a31483c2-ora-u02"
> device-mapper: table: 253:1: multipath: error getting device
> device-mapper: ioctl: error adding target to table
> qla4xxx: invalid ioctl magic number received.
> qla4xxx: invalid ioctl magic number received.
> qla4xxx: invalid ioctl magic number received.
> qla4xxx: invalid ioctl magic number received.
>
> First of all, I appologise if this isn't the right place to post
> QLogic HBA questions, but I saw others were doing it so I hope it's
> ok.
>
> My hardware:
> Two QLogic iSCSI HBA QLE4062C (dual port) cards, each installed in a
> Dell PE2950 server. Connected to a cisco gigabit switch (seperate
> vlan) and a Dell EqualLogic PS5000XV iSCSI SAN. Each server has CentOS
> 5 x86_64 (v5.1 with latest updates installed).
>
> I've (tried to) configured my servers for multipath iscsi shared
> storage (will be a cluster setup when done). In my message log I get
> these errors (first two lines aren't an error though):
>
> qla4xxx 0000:09:01.1: DDB[2] MB0 4000 Tot 1 Next 0 State 0004 ConnErr
> 00000000 172.2x.yy.10:3260 "iqn.2001-05.com.equallogic:
> 0-8a0906-6accc8302-9ef00000a31483c2-ora-u02"
> qla4xxx 0000:09:01.3: DDB[2] MB0 4000 Tot 1 Next 0 State 0004 ConnErr
> 00000000 172.2x.yy.10:3260 "iqn.2001-05.com.equallogic:
> 0-8a0906-6accc8302-9ef00000a31483c2-ora-u02"
> device-mapper: table: 253:1: multipath: error getting device
> device-mapper: ioctl: error adding target to table
> qla4xxx: invalid ioctl magic number received.
> qla4xxx: invalid ioctl magic number received.
> qla4xxx: invalid ioctl magic number received.
> qla4xxx: invalid ioctl magic number received.
>
You might want to email David Somayajulu <david.so...@qlogic.com>.
He is the maintainer of qla4xxx and the error message comes from some
qlogic.com code, so he will know best.
David Somayajulu
May 29, 2008, 10:15:36 PM5/29/08
to Mike Christie, open-...@googlegroups.com
Joffer, Would you mind sending me the driver version.
Joffer
May 30, 2008, 12:55:23 AM5/30/08
to open-iscsi
On May 29, 10:15 pm, "David Somayajulu" <david.somayaj...@qlogic.com>
wrote:
to date (v5.1).
wrote:
> > You might want to email David Somayajulu
>
> <david.somayaj...@qlogic.com>.> He is the maintainer of qla4xxx and the error message comes from some
>
> > qlogic.com code, so he will know best.
>
> Joffer, Would you mind sending me the driver version.
>
> Joffer, Would you mind sending me the driver version.
SANsurfer Linux iSCSI Driver Installer (x86/x64) - v5.01.01.04-1
The one from qlogic.com website. Any other info you want? CentOS is up
to date (v5.1).
Joffer
May 30, 2008, 1:05:16 AM5/30/08
to open-iscsi
better to post too much than too little, at least since I'm off to bed
now (I'm in Norway), so it'll be a few hours before I can reply
again..
[root@linux02 ~]# modinfo qla4xxx
filename: /lib/modules/2.6.18-53.1.21.el5/kernel/drivers/scsi/
qla4xxx/qla4xxx.ko
license: GPL
description: QLogic ISP4XXX iSCSI Host Bus Adapter driver
author: QLogic Corporation
srcversion: C2F4E58491D8E255655BB4D
alias: pci:v00001077d00004032sv*sd*bc*sc*i*
alias: pci:v00001077d00004022sv*sd*bc*sc*i*
alias: pci:v00001077d00004010sv*sd*bc*sc*i*
depends: scsi_mod
vermagic: 2.6.18-53.1.21.el5 SMP mod_unload gcc-4.1
parm: ql4xfailover:Driver failover support: 0 to disable; 1
to enable. (int)
parm: recoveryTime:Recovery time in seconds before a target
device is sent I/O after a failback is performed. (int)
parm: failbackTime:Delay in seconds before a failback is
performed. (int)
parm: MaxPathsPerDevice:Maximum number of paths to a
device. Default 8. (int)
parm: MaxRetriesPerPath:How many retries to perform on the
current path before failing over to the next path in the path list.
(int)
parm: MaxRetriesPerIo:How many total retries to do before
failing the command and returning to the OS with a DID_NO_CONNECT
status. (int)
parm: qlFailoverNotifyType:Failover notification mechanism
to use when a failover or failback occurs. (int)
parm: ql4xdiscoverywait:Discovery wait time (int)
parm: ql4xkeepalive:Keep Alive Timeout (int)
parm: ql4xdontresethba:Dont reset the HBA when the driver
gets 0x8002 AEN default it will reset hba :0 set to 1 to avoid
resetting HBA (int)
parm: ql4xcmdretrycount:Maximum number of mid-layer retries
allowed for a command. Default value in non-failover mode is 20, in
failover mode, 30. (int)
parm: ql4xqfullrampup:Number of seconds to wait to begin to
ramp-up the queue depth for a device after a queue-full condition has
been detected. Default is 120 seconds. (int)
parm: ql4xmaxqdepth:Maximum queue depth to report for target
devices. (int)
parm: extended_error_logging:Option to enable extended error
logging, Default is 0 - no logging. 1 - log errors. 2 - debug logging
(int)
parm: displayConfig:If 1 then display the configuration used
in /etc/modules.conf. (int)
dmesg (the first port on the card):
QLogic iSCSI HBA Driver (ffffffff88119000)
GSI 20 sharing vector 0x5A and IRQ 20
ACPI: PCI Interrupt 0000:09:01.1[B] -> GSI 19 (level, low) -> IRQ 90
qla4xxx 0000:09:01.1: Found an ISP4032, irq 0, iobase
0xffffc2000001a000
qla4xxx 0000:09:01.1: Configuring PCI space...
qla4xxx 0000:09:01.1: Configuring NVRAM ...
qla4xxx 0000:09:01.1: Initializing firmware..
qla4xxx 0000:09:01.1: Waiting for Firmware Ready..
qla4xxx 0000:09:01.1: Firmware Ready..
qla4xxx 0000:09:01.1: Initializing DDBs ...
qla4xxx 0000:09:01.1: DDB[0] MB0 4000 Tot 1 Next 2 State 0000 ConnErr
00000000 0.0.0.0:3260 ""
qla4xxx 0000:09:01.1: DDB[0] MB0 4000 Tot 1 Next 2 State 0000 ConnErr
00000000 0.0.0.0:3260 ""
qla4xxx 0000:09:01.1: DDB[2] MB0 4000 Tot 1 Next 0 State 0004 ConnErr
00000000 172.2x.yy.10:3260 "iqn.2001-05.com.equallogic:
0-8a0906-6accc8302-9ef00000a31483c2-ora-u02"
qla4xxx 0000:09:01.1: DDB[2] MB0 4000 Tot 1 Next 0 State 0004 ConnErr
00000000 172.2x.yy.10:3260 "iqn.2001-05.com.equallogic:
0-8a0906-6accc8302-9ef00000a31483c2-ora-u02"
qla4xxx 0000:09:01.1: DDB list done..
00000000 172.2x.yy.10:3260 "iqn.2001-05.com.equallogic:
0-8a0906-6accc8302-9ef00000a31483c2-ora-u02"
qla4xxx 0000:09:01.1: DDB[2] MB0 4000 Tot 1 Next 0 State 0004 ConnErr
00000000 172.2x.yy.10:3260 "iqn.2001-05.com.equallogic:
0-8a0906-6accc8302-9ef00000a31483c2-ora-u02"
scsi-qla0-mac=00c0dd0bd785\;
scsi3 : qla4xxx
QLogic iSCSI HBA Driver version: 5.01.01.04
QLogic ISP4032 @ 0000:09:01.1 hdma+, host#=3, fw=03.00.01.24
Vendor: EQLOGIC Model: 100E-00 Rev: 3.3
Type: Direct-Access ANSI SCSI revision: 05
qla4xxx 0000:09:01.1: scsi(3:0:1:0): Enabled tagged queuing, queue
depth 32.
SCSI device sdc: 524298240 512-byte hdwr sectors (268441 MB)
sdc: Write Protect is off
sdc: Mode Sense: 81 00 00 00
SCSI device sdc: drive cache: write through
SCSI device sdc: 524298240 512-byte hdwr sectors (268441 MB)
sdc: Write Protect is off
sdc: Mode Sense: 81 00 00 00
SCSI device sdc: drive cache: write through
sdc: unknown partition table
sd 3:0:1:0: Attached scsi disk sdc
Joffer
May 30, 2008, 2:31:26 PM5/30/08
to open-iscsi
I removed the QLogic supplied driver and restarted. Now the in-kernel
qla4xxx module was loaded. dmesg gave me the same error message as the
QLogic one:
device-mapper: table: 253:0: multipath: error getting device
qla4xxx module was loaded. dmesg gave me the same error message as the
QLogic one:
device-mapper: table: 253:0: multipath: error getting device
device-mapper: ioctl: error adding target to table
/ChristopherMike Christie
May 30, 2008, 11:04:57 PM5/30/08
to open-...@googlegroups.com
I misread the mail. I thought the problem was the qla4xx ioctl modules
errors. For the multipath ones you will want to post to dm-devel.
Joffer
Jun 2, 2008, 12:25:50 AM6/2/08
to open-iscsi
same error with the kernel module after I removed the qlogic driver.
Perhaps David or somebody else has a solution tough... I will go to dm-
devel with my problem tough.
Reply all
Reply to author
Forward
0 new messages