frank.vandamme | 19 Mar 15:55 2014
Picon

connection back, disk gone

Hi list,

I had some trouble with an iscsi disk that lost its connection to the target. I am running xfs on lvm on iscsi (on Debian 7.0 amd64). The connection came back up OK after 10 minutes or so:

iscsid: connection1:0 is operational after recovery (31 attempts)

but disk only came back after I restarted open-iscsid using the init script. After that, the disk shows up in my kernel log, lvm got back on its feet and the file system was mounted again.

I'm interested to know why, when the connection is restored, the session associated with it aren't restored as well? After all, what you want after a couple minutes of network failure is just to have your disk back, correct?

Greetings,

--
Frank Van Damme

--
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.
John Soni Jose | 21 Mar 10:59 2014

[PATCH 0/2] iscsi tools: Fixes for be2iscsi and StatSN

 Following are the patches which fixes
  - be2iscsi MaxXmitDataLength when target returns MRDSL=0
  - Fix StatSN data type

John Soni Jose (2):
  be2iscsi: Fix MaxXmitDataLenght of the driver.
  Fix StatSN in Open-iSCSI Stack.

 usr/be2iscsi.c         |    4 ----
 usr/initiator_common.c |    2 +-
 usr/iscsi_ipc.h        |    1 +
 usr/netlink.c          |    3 +++
 4 files changed, 5 insertions(+), 5 deletions(-)

-- 
1.7.4.1

--

-- 
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe@...
To post to this group, send email to open-iscsi@...
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.

Sony John-N | 17 Mar 06:39 2014

RE: Error on discovery using emulex be2iscsi

Hi

 

Looks like initiator is not able to establish a TCP_CXN with the target.

Can the wire-trace during discovery command be captured and provided for debugging the issue.

 

Had few queries regarding the setup

-          Is the initiator-name set in /etc/iscsi path.

-          Is the IP address set on the initiator port. If IP is set can a ping from target machine to the initiator IP be tried out.

-          Please provide the wire-trace when discovery command was issued.

 

-Sony

 

From: open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org [mailto:open-iscsi <at> googlegroups.com] On Behalf Of adebarbara
Sent: Friday, March 14, 2014 12:33 PM
To: open-iscsi <at> googlegroups.com
Subject: Error on discovery using emulex be2iscsi

 

Hi guys,

 

I am hitting an issue where I could not even discovery targets using be2iscsi driver.

So If someone are using emulex on HP Proliant servers and have any hint on what is going please drop me a line. 

 

The following is the output I get when I load the kernel driver and trying to discover on a target running ilo (tgt do the same).

 

My system 

 

Kernel : Linux 3.9.6-030906-generic #201306131535 SMP Thu Jun 13 19:35:54 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Controller : Mass storage controller: Emulex Corporation OneConnect 10Gb iSCSI Initiator (rev 02)

Emulex driver: Emulex OneConnectOpen-iSCSI Driver version10.0.272.0

Distro : Ubuntu 12.10

 

Thanks in advance!

 

 

------

 

modprobe be2iscsi


[10835.048474] scsi17 : Emulex 10Gbe open-iscsi Initiator Driver
[10835.049145] be2iscsi 0000:05:00.2: irq 112 for MSI/MSI-X
[10835.049164] be2iscsi 0000:05:00.2: irq 113 for MSI/MSI-X
[10835.049188] be2iscsi 0000:05:00.2: irq 114 for MSI/MSI-X
[10835.049204] be2iscsi 0000:05:00.2: irq 115 for MSI/MSI-X
[10835.049220] be2iscsi 0000:05:00.2: irq 116 for MSI/MSI-X
[10835.049236] be2iscsi 0000:05:00.2: irq 117 for MSI/MSI-X
[10835.049251] be2iscsi 0000:05:00.2: irq 118 for MSI/MSI-X
[10835.049266] be2iscsi 0000:05:00.2: irq 119 for MSI/MSI-X
[10840.391427] scsi host17: BC_174 : MBX Cmd Completion timed out
[10840.402716] scsi host17: BG_1163 : MBX CMD get_boot_target Failed
[10840.413885] scsi host17: BM_3880 : No boot session
[10840.436963] scsi host17: BC_174 : MBX Cmd Completion timed out
[10840.447943] scsi host17: BG_751 : mgmt_exec_nonemb_cmd Failed status
[10840.470781] scsi host17: BC_174 : MBX Cmd Completion timed out
[10840.481637] scsi host17: BG_751 : mgmt_exec_nonemb_cmd Failed status

iscsiadm -m discovery -I be2iscsi.38:ea:a7:a5:62:89.ipv4.0 -p 10.70.3.250 -t st

Mar 13 17:49:56 e31-host02 kernel: [10946.559435] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:49:56 e31-host02 kernel: [10946.569905] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:49:56 e31-host02 kernel: [10946.580209] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
Mar 13 17:49:57 e31-host02 kernel: [10947.615583] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:49:57 e31-host02 kernel: [10947.626074] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:49:57 e31-host02 kernel: [10947.636385] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
Mar 13 17:49:58 e31-host02 kernel: [10948.672143] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:49:58 e31-host02 kernel: [10948.682591] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:49:58 e31-host02 kernel: [10948.692899] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
Mar 13 17:49:59 e31-host02 kernel: [10949.730847] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:49:59 e31-host02 kernel: [10949.741342] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:49:59 e31-host02 kernel: [10949.751655] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
Mar 13 17:50:00 e31-host02 snmpd[10412]: error on subcontainer
'ia_addr' insert (-1)
Mar 13 17:50:00  snmpd[10412]: last message repeated 2 times
Mar 13 17:50:00 e31-host02 kernel: [10950.787615] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:50:00 e31-host02 kernel: [10950.798721] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:50:00 e31-host02 kernel: [10950.809107] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
Mar 13 17:50:01 e31-host02 kernel: [10951.845008] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:50:01 e31-host02 kernel: [10951.855527] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:50:01 e31-host02 kernel: [10951.865858] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
iscsiadm: connection login retries (reopen_max) 5 exceeded
iscsiadm: No portals found

 

 

--
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.

John Soni Jose | 21 Mar 09:56 2014

[PATCH 0/2] iscsi tools: Fixes for be2iscsi and StatSN

 Following are the patches which fixes
  - be2iscsi MaxXmitDataLength when target returns MRDSL=0
  - Fix StatSN data type

John Soni Jose (2):
  be2iscsi: Fix MaxXmitDataLenght of the driver.
  Fix StatSN in Open-iSCSI Stack.

 usr/be2iscsi.c         |    4 ----
 usr/initiator_common.c |    2 +-
 usr/iscsi_ipc.h        |    1 +
 usr/netlink.c          |    3 +++
 4 files changed, 5 insertions(+), 5 deletions(-)

-- 
1.7.4.1

--

-- 
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe@...
To post to this group, send email to open-iscsi@...
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.

John Soni Jose | 21 Mar 11:00 2014

[PATCH 1/2] be2iscsi: Fix MaxXmitDataLenght of the driver.

 Issue :
 During login negotiation if the MaxRecvDataSegmenLen given by the
 target is 0, then MRDSL default value of 8K should be considered.
 Some old targets close the CXN if the PDU received size is greater
 than the MaxRecvDataSegmentLen set during negotiation.

 Fix :
 When target is not sending MaxRecvDataSegmentLen in the negotiated
 params the value is 0. be2iscsi was setting max_xmit_dlength to 64k
 in this case. This fix sets the MaxRecvDataSegmentLen=8k if during
 negotiation the MaxRecvDataSegmentLen=0

Signed-off-by: John Soni Jose <sony.john-n@...>
Signed-off-by: Jayamohan Kallickal <jayamohan.kallickal@...>
---
 usr/be2iscsi.c |    4 ----
 1 files changed, 0 insertions(+), 4 deletions(-)

diff --git a/usr/be2iscsi.c b/usr/be2iscsi.c
index ce8b719..ba4c29f 100644
--- a/usr/be2iscsi.c
+++ b/usr/be2iscsi.c
 <at>  <at>  -33,10 +33,6  <at>  <at>  void be2iscsi_create_conn(struct iscsi_conn *conn)
 	if (conn->max_xmit_dlength > 65536)
 		conn->max_xmit_dlength = 65536;

-	if (!conn_rec->iscsi.MaxXmitDataSegmentLength ||
-	    conn_rec->iscsi.MaxXmitDataSegmentLength > 65536)
-		conn_rec->iscsi.MaxXmitDataSegmentLength = 65536;
-
 	session->erl = 0;
 	session->initial_r2t_en = 1;
 }
-- 
1.7.4.1

--

-- 
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe@...
To post to this group, send email to open-iscsi@...
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.

John Soni Jose | 21 Mar 07:21 2014

[PATCH 1/2] be2iscsi: Fix MaxXmitDataLenght of the driver.

 Issue :
 During login negotiation if the MaxRecvDataSegmenLen given by the
 target is 0, then MRDSL default value of 8K should be considered.
 Some old targets close the CXN if the PDU received size is greater
 than the MaxRecvDataSegmentLen set during negotiation.

 Fix :
 When target is not sending MaxRecvDataSegmentLen in the negotiated
 params the value is 0. be2iscsi was setting max_xmit_dlength to 64k
 in this case. This fix sets the MaxRecvDataSegmentLen=8k if during
 negotiation the MaxRecvDataSegmentLen=0

Signed-off-by: John Soni Jose <sony.john-n@...>
Signed-off-by: Jayamohan Kallickal <jayamohan.kallickal@...>
---
 usr/be2iscsi.c |    4 ----
 1 files changed, 0 insertions(+), 4 deletions(-)

diff --git a/usr/be2iscsi.c b/usr/be2iscsi.c
index ce8b719..ba4c29f 100644
--- a/usr/be2iscsi.c
+++ b/usr/be2iscsi.c
 <at>  <at>  -33,10 +33,6  <at>  <at>  void be2iscsi_create_conn(struct iscsi_conn *conn)
 	if (conn->max_xmit_dlength > 65536)
 		conn->max_xmit_dlength = 65536;

-	if (!conn_rec->iscsi.MaxXmitDataSegmentLength ||
-	    conn_rec->iscsi.MaxXmitDataSegmentLength > 65536)
-		conn_rec->iscsi.MaxXmitDataSegmentLength = 65536;
-
 	session->erl = 0;
 	session->initial_r2t_en = 1;
 }
-- 
1.7.4.1

--

-- 
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe@...
To post to this group, send email to open-iscsi@...
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.

John Soni Jose | 21 Mar 07:21 2014

[PATCH 2/2] Fix StatSN in Open-iSCSI Stack.

From: John Soni Jose <jose0here@...>

 When LIO target is used, STATSN in login response can be in
 the range 0x0 - 0xFFFFFFFF. Open-iSCSI Stack had the type
 as ISCSI_INT for StatSN, so StatSN used to get reset to 0.

 Adding new type ISCSI_UINT feild to fix this issue.

Signed-off-by: John Soni Jose <sony.john-n@...>
Signed-off-by: Jayamohan Kallickal <jayamohan.kallickal@...>
---
 usr/initiator_common.c |    2 +-
 usr/iscsi_ipc.h        |    1 +
 usr/netlink.c          |    3 +++
 3 files changed, 5 insertions(+), 1 deletions(-)

diff --git a/usr/initiator_common.c b/usr/initiator_common.c
index 109e8d7..50f8d41 100644
--- a/usr/initiator_common.c
+++ b/usr/initiator_common.c
 <at>  <at>  -431,7 +431,7  <at>  <at>  int iscsi_session_set_neg_params(struct iscsi_conn *conn)
 		}, {
 			.param = ISCSI_PARAM_EXP_STATSN,
 			.value = &conn->exp_statsn,
-			.type = ISCSI_INT,
+			.type = ISCSI_UINT,
 			.conn_only = 1,
 		}, {
 			.param = ISCSI_PARAM_TPGT,
diff --git a/usr/iscsi_ipc.h b/usr/iscsi_ipc.h
index 9d26d54..5087b5c 100644
--- a/usr/iscsi_ipc.h
+++ b/usr/iscsi_ipc.h
 <at>  <at>  -30,6 +30,7  <at>  <at> 

 enum {
 	ISCSI_INT,
+	ISCSI_UINT,
 	ISCSI_STRING,
 };

diff --git a/usr/netlink.c b/usr/netlink.c
index 532d9ef..b0dfb03 100644
--- a/usr/netlink.c
+++ b/usr/netlink.c
 <at>  <at>  -716,6 +716,9  <at>  <at>  kset_param(uint64_t transport_handle, uint32_t sid, uint32_t cid,
 	case ISCSI_INT:
 		sprintf(param_str, "%d", *((int *)value));
 		break;
+	case ISCSI_UINT:
+		sprintf(param_str, "%u", *((unsigned int *)value));
+		break;
 	case ISCSI_STRING:
 		if (!strlen(value))
 			return 0;
-- 
1.7.4.1

--

-- 
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe@...
To post to this group, send email to open-iscsi@...
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.

Chris Leech | 27 Mar 16:51 2014
Picon

Re: [PATCH 7/7] actor: Don't wake up poll() on a timeout if we don't need to

On Thu, Mar 27, 2014 at 11:27:07AM -0400, Adam Jackson wrote:
> Is there any hope for this patch series to go in?  It's rather
> unpleasant to have the daemon waking up four times a second when there's
> no work to do, it keeps your processor out of deep C states and if you
> have enough virtual machines it's a density problem.

Mike correctly pointed out that there's an issue with the
reap_proc/waitpid routines not being called.  I never finished
revisiting that.

- Chris

--

-- 
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe@...
To post to this group, send email to open-iscsi@...
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.

Gaofeng | 6 Mar 03:33 2014
Picon

oops in sd_probe_async

1) my kernel is 2.6.32-71.el6 (centos)
2) the stack of panic:
   Call Trace:
 [<ffffffff811de547>] sysfs_add_file_mode+0x57/0xb0
 [<ffffffff811de5b1>] sysfs_add_file+0x11/0x20
 [<ffffffff811de5e6>] sysfs_create_file+0x26/0x30
 [<ffffffff81238713>] elv_register_queue+0x63/0x90
 [<ffffffff812428d3>] blk_register_queue+0xb3/0x100
 [<ffffffff812484a4>] add_disk+0x94/0x160
 [<ffffffffa01a332b>] sd_probe_async+0x13b/0x210 [sd_mod]
 [<ffffffff81091d86>] ? add_wait_queue+0x46/0x60
 [<ffffffff81098dc2>] async_thread+0x102/0x250
 [<ffffffff8105c230>] ? default_wake_function+0x0/0x20
 [<ffffffff81098cc0>] ? async_thread+0x0/0x250
 [<ffffffff810916c6>] kthread+0x96/0xa0
 [<ffffffff810141ca>] child_rip+0xa/0x20
 [<ffffffff81091630>] ? kthread+0x0/0xa0
 [<ffffffff810141c0>] ? child_rip+0x0/0x20
Code: fb 49 89 f4 48 c7 47 08 00 00 00 00 48 c7 47 10 00 00 00 00 48 c7 47 18 00 00 00 00 48 c7 c7 e0 92 77 81 48 89 33 e8 03 98 2e 00 <49> 8b 74 24 38 48 8b 3d 7f 81 a1 00 4c 89 e1 48 c7 c2 10 ee 1d  RIP  [<ffffffff811df15d>] sysfs_addrm_start+0x3d/0xd0

3) 
4) I think this panic is caused by parallel of sd_probe and sd_remove in sd_mod
5) in the sd_remove of kernel 2.6.36, there is  "scsi_autopm_get_device".
   Do this function can solve the panic?

--
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.
adebarbara | 14 Mar 20:33 2014
Picon

Error on discovery using emulex be2iscsi

Hi guys,

I am hitting an issue where I could not even discovery targets using be2iscsi driver.
So If someone are using emulex on HP Proliant servers and have any hint on what is going please drop me a line. 
 
The following is the output I get when I load the kernel driver and trying to discover on a target running ilo (tgt do the same).

My system 

Kernel : Linux 3.9.6-030906-generic #201306131535 SMP Thu Jun 13 19:35:54 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Controller : Mass storage controller: Emulex Corporation OneConnect 10Gb iSCSI Initiator (rev 02)
Emulex driver: Emulex OneConnectOpen-iSCSI Driver version10.0.272.0
Distro : Ubuntu 12.10

Thanks in advance!


------

modprobe be2iscsi

[10835.048474] scsi17 : Emulex 10Gbe open-iscsi Initiator Driver
[10835.049145] be2iscsi 0000:05:00.2: irq 112 for MSI/MSI-X
[10835.049164] be2iscsi 0000:05:00.2: irq 113 for MSI/MSI-X
[10835.049188] be2iscsi 0000:05:00.2: irq 114 for MSI/MSI-X
[10835.049204] be2iscsi 0000:05:00.2: irq 115 for MSI/MSI-X
[10835.049220] be2iscsi 0000:05:00.2: irq 116 for MSI/MSI-X
[10835.049236] be2iscsi 0000:05:00.2: irq 117 for MSI/MSI-X
[10835.049251] be2iscsi 0000:05:00.2: irq 118 for MSI/MSI-X
[10835.049266] be2iscsi 0000:05:00.2: irq 119 for MSI/MSI-X
[10840.391427] scsi host17: BC_174 : MBX Cmd Completion timed out
[10840.402716] scsi host17: BG_1163 : MBX CMD get_boot_target Failed
[10840.413885] scsi host17: BM_3880 : No boot session
[10840.436963] scsi host17: BC_174 : MBX Cmd Completion timed out
[10840.447943] scsi host17: BG_751 : mgmt_exec_nonemb_cmd Failed status
[10840.470781] scsi host17: BC_174 : MBX Cmd Completion timed out
[10840.481637] scsi host17: BG_751 : mgmt_exec_nonemb_cmd Failed status

iscsiadm -m discovery -I be2iscsi.38:ea:a7:a5:62:89.ipv4.0 -p 10.70.3.250 -t st

Mar 13 17:49:56 e31-host02 kernel: [10946.559435] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:49:56 e31-host02 kernel: [10946.569905] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:49:56 e31-host02 kernel: [10946.580209] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
Mar 13 17:49:57 e31-host02 kernel: [10947.615583] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:49:57 e31-host02 kernel: [10947.626074] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:49:57 e31-host02 kernel: [10947.636385] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
Mar 13 17:49:58 e31-host02 kernel: [10948.672143] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:49:58 e31-host02 kernel: [10948.682591] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:49:58 e31-host02 kernel: [10948.692899] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
Mar 13 17:49:59 e31-host02 kernel: [10949.730847] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:49:59 e31-host02 kernel: [10949.741342] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:49:59 e31-host02 kernel: [10949.751655] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
Mar 13 17:50:00 e31-host02 snmpd[10412]: error on subcontainer
'ia_addr' insert (-1)
Mar 13 17:50:00  snmpd[10412]: last message repeated 2 times
Mar 13 17:50:00 e31-host02 kernel: [10950.787615] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:50:00 e31-host02 kernel: [10950.798721] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:50:00 e31-host02 kernel: [10950.809107] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
Mar 13 17:50:01 e31-host02 kernel: [10951.845008] scsi host15: BC_206
: MBX Cmd Failed for Subsys : 6 Opcode : 52 with Status : 32 and
Extd_Status : 1
Mar 13 17:50:01 e31-host02 kernel: [10951.855527] scsi host15: BS_1073
: mgmt_open_connection Failed
Mar 13 17:50:01 e31-host02 kernel: [10951.865858] scsi host15: BS_1141
: Failed in beiscsi_open_conn
iscsiadm: Received iferror -16: Device or resource busy.
iscsiadm: Connection to discovery portal 10.70.3.250 failed:
encountered connection failure
iscsiadm: connection login retries (reopen_max) 5 exceeded
iscsiadm: No portals found


--
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.
Muthu Kumaran | 16 Mar 10:20 2014
Picon

ISCSI error in centos 6


Hi,

I am trying to configure ISCSI storage in my vm ware, But when tried to login to the ISCSI target from the client it throws the following errors.

[root <at> localhost ~]# iscsiadm --mode discoverydb --type sendtargets --portal 192.168.40.130 --discover
iscsiadm: cannot make connection to 192.168.40.130: No route to host
iscsiadm: cannot make connection to 192.168.40.130: No route to host
iscsiadm: cannot make connection to 192.168.40.130: No route to host
iscsiadm: cannot make connection to 192.168.40.130: No route to host
iscsiadm: cannot make connection to 192.168.40.130: No route to host
iscsiadm: cannot make connection to 192.168.40.130: No route to host
iscsiadm: connection login retries (reopen_max) 5 exceeded
iscsiadm: Could not perform SendTargets discovery: encountered connection failure
[root <at> localhost ~]#


#iscsiadm -m node -L all
Logging in to [iface: default, target: iqn.2014-03.sharedstorage:target1, portal: 192.168.40.130,3260] (multiple)
iscsiadm: Could not login to [iface: default, target: iqn.2014-03.sharedstorage:target1, portal: 192.168.40.130,3260].
iscsiadm: initiator reported error (8 - connection timed out)
iscsiadm: Could not log into all portals

Can any one help me to sort out this issue ?

Thanks!

--
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.

Gmane