.
What target is this with?
On 07/22/2014 09:42 PM, 木木夕 wrote:
hello everyone,
the iscsi initiator can login the iscsi target successfully, everything
looks well
but when i start to read I/O(dd if=/dev/sdb of=/dev/null bs=512k), it
will print
connection1:0: detected conn error
/sdb of=/dev/null bs=512k), it
will print
connection1:0: detected conn error (1011)
it happened many times
any reply will be welcome
--
You received this message because you are subscribed to the Google
Groups open-iscsi group.
To unsubscribe
hello everyone,
the iscsi initiator can login the iscsi target successfully, everything
looks well
but when i start to read I/O(dd if=/dev/sdb of=/dev/null bs=512k), it will
print
connection1:0: detected conn error (1011)
it happened many times
any reply will be welcome
--
You received
On 12/14/2010 03:12 PM, p...@fhri.org wrote:
Hi all...
I have four CentOS 5.4 (2.6.18-164.11.1.el5) servers with iscsid version
2.0-871. Two are misbehaving despite identical configuration. They all
connect to Enhance Tech RS8-IP4 array the same way, directly NIC-to-NIC
without a switch,
: connection19:0: iscsi: detected conn error
(1011)
Sep 7 16:08:23 hostname kernel: connection31:0: iscsi: detected conn error
(1011)
Sep 7 16:08:23 hostname kernel: connection20:0: iscsi: detected conn error
(1011)
Sep 7 16:08:23 hostname kernel: connection32:0: iscsi: detected conn error
(1011)
Sep
Sorry,
this message was intended for someone else. E-Mail program tricked me. -- Ulrich
Ulrich Windl ulrich.wi...@rz.uni-regensburg.de schrieb am 08.09.2010 um
13:51 in Nachricht 4c8794da02a1f...@gwsmtp1.uni-regensburg.de:
--
You received this message because you are subscribed to
On Thu, Sep 02, 2010 at 03:15:31PM -0700, Shantanu Mehendale wrote:
Hi Hannes/Mike,
I am also dealing with another issue on ISCSI transport where I am
seeing DID_TRASNPORT_FAILFAST hostbyte errors reaching the application
which is sending I/O on a device-mapper node. Reading the code a
' with regards to the issue, though!
Thanks,
-Goncalo.
-Original Message-
From: Hannes Reinecke [mailto:h...@suse.de]
Sent: 30 August 2010 15:12
To: Goncalo Gomes
Cc: Mike Christie; open-iscsi@googlegroups.com; Shantanu Mehendale
Subject: Re: detected conn error (1011)
Goncalo Gomes wrote
Goncalo Gomes wrote:
Hi Hannes,
Thanks. The Citrix XenServer 5.6 distribution kernel is based on the 2.6.27
tree of SLES 11.
We add a few extra patches specific to Xen, dom0 integration and some
backports from upstream.
To the best of my knowledge these additions don't touch the iscsi
Thanks Hannes and Mike,
Your help has been highly appreciated!
Cheers,
-Goncalo.
-Original Message-
From: Hannes Reinecke [mailto:h...@suse.de]
Sent: 31 August 2010 14:43
To: Goncalo Gomes
Cc: Mike Christie; open-iscsi@googlegroups.com; Shantanu Mehendale
Subject: Re: detected conn
Goncalo Gomes wrote:
Hi,
On Fri, 2010-08-06 at 15:57 +0100, Hannes Reinecke wrote:
Mike Christie wrote:
ccing Hannes from suse, because this looks like a SLES only bug.
Hey Hannes,
The user is using Linux 2.6.27 x86 based on SLES + Xen 3.4 (as dom0)
running a couple of RHEL 5.5 VMs.
connection1:0: detected conn error (1011)
scsi 6:0:0:0: Direct-Access EQLOGIC 100E-00 4.3 PQ: 0 ANSI: 5
sd 6:0:0:0: [sdb] 209725440 512-byte hardware sectors: (107 GB/100 GiB)
sd 6:0:0:0: [sdb] Write Protect is off
sd 6:0:0:0: [sdb] Mode Sense: ad 00 00 00
sd 6:0:0:0: [sdb] Write cache
: Re: detected conn error (1011)
Mike Christie wrote:
ccing Hannes from suse, because this looks like a SLES only bug.
Hey Hannes,
The user is using Linux 2.6.27 x86 based on SLES + Xen 3.4 (as dom0)
running a couple of RHEL 5.5 VMs. The underlying storage for these VMs
is iSCSI based via
On 08/06/2010 09:57 AM, Hannes Reinecke wrote:
Mike Christie wrote:
ccing Hannes from suse, because this looks like a SLES only bug.
Hey Hannes,
The user is using Linux 2.6.27 x86 based on SLES + Xen 3.4 (as dom0)
running a couple of RHEL 5.5 VMs. The underlying storage for these VMs
is iSCSI
On 08/06/2010 11:38 AM, Mike Christie wrote:
It should stall, It works like FC and the fast io fail tmo. Users need
to set the iscsi replacement/recovery timeout like they would FC's fast
io fail tmo. They should set it to 3 or 5 secs or lower if they want
really fast failovers.
Oh yeah,
Goncalo Gomes goncalo.go...@eu.citrix.com schrieb am 04.08.2010 um 23:12
in
Nachricht
ffdb98dc9661d3418b9eb0ff5202e46b7a82e8b...@lonpmailbox01.citrite.net:
I'm running a setup composed of: Linux 2.6.27 x86 based on SLES + Xen 3.4 (as
dom0) running a couple of RHEL 5.5 VMs. The underlying
On Thu, 2010-08-05 at 08:50 +0200, Ulrich Windl wrote:
I guess that's SLES11 already. I just read an announcement that there is an
opne-iscsi update for SLES11 SP1 available. Unfortunately Novell does not
give any details in the announcements:
4. Recommended update for open-iscsi
On Wed, 2010-08-04 at 21:51 -0500, Mike Christie wrote:
conn error 1011 is generic. If this is occurring when the eql box is
rebalancing luns, it is a little different than above. With the above
problem we did not know why we got the error. With your situation we
sort of expect this. We
the controllers/ports, it
requests the initiator to logout and login again to the new port/ip. If the
guests are idle, the following messages show up in the logs:
Aug 3 17:55:08 goncalog140 kernel: connection1:0: detected conn error (1011)
Aug 3 17:55:09 goncalog140 kernel: connection1:0: detected
the equallogic rebalances the LUNs between the controllers/ports, it
requests the initiator to logout and login again to the new port/ip. If the
guests are idle, the following messages show up in the logs:
Aug 3 17:55:08 goncalog140 kernel: connection1:0: detected conn error (1011)
Aug 3 17:55:09
Ulrich Windl ulrich.wi...@rz.uni-regensburg.de schrieb am
28.07.2010
um
16:46 in Nachricht 4c505ef502a1e...@gwsmtp1.uni-regensburg.de
:
Sean S sstra...@gmail.com schrieb am 28.07.2010 um 16:34 in
Nachricht
f711789b-c411-4459-afbe-fe1a50fe2...@w12g2000yqj.googlegroups.
com:
On 07/28/2010 09:34 AM, Sean S wrote:
What version of open-iscsi-871 are you using is it 871.1 or .2 .3?
I downloaded the current semi-stable release:
http://www.open-iscsi.org/bits/open-iscsi-2.0-871.tar.gz
It doesn't appear to have a minor version number. Should I be using
something else?
Sean S sstra...@gmail.com schrieb am 27.07.2010 um 00:37 in
Nachricht
109cc690-901c-4e53-9fa9-1a9903380...@l14g2000yql.googlegroups.
com:
[...]
I'm unable to view /var/log/messages after the failure due to running
as iscsi root. Ulrich mentioned writing the log to a serial port, but
I
+0x24d/0x422 [scsi_mod]
[c041f7ea] complete+0x2b/0x3d
[f885e610] scsi_error_handler+0x0/0x422 [scsi_mod]
[c0435f65] kthread+0xc0/0xeb
[c0435ea5] kthread+0x0/0xeb
[c0405c3b] kernel_thread_helper+0x7/0x10
===
connection1:0 detected conn error (1011)
[f8bf0876
On 07/26/2010 04:36 PM, Sean S wrote:
Thanks for the patch Mike. Below is the output from a failure when
running with the patch. Any thoughts?
[f8bf0876] iscsi_conn_failure+0x10/0x69 [libiscsi]
[f9bf202d] iscsi_eh_abort+0x2f1/0x406 [libiscsi]
[f885d378] __scsi_try_to_abort_cmd+0x19/0x1a
Sean S sstra...@gmail.com schrieb am 13.07.2010 um 20:41 in Nachricht
1f2389e7-9717-4f82-a05c-671f36a4c...@x21g2000yqa.googlegroups.com:
I'm running an iscsi root partition for a CentOS machine running a
2.6.18-53 kernel. Every couple of days I get the error:
connection1:0 detected conn
Sean S sstra...@gmail.com schrieb am 14.07.2010 um 04:33 in Nachricht
83cd8c40-2e84-4c52-a864-36643dd0a...@d8g2000yqf.googlegroups.com:
Nothing else in the log from iscsid. No mention of a failed reconnect,
although the only log I'm really able to access post failure is dmesg.
Since I'm
the error:
connection1:0 detected conn error (1011)
session1: session recovery timed out after 400 sec
Hi!
I cannot answer your question, but that brings up something I wanted to talk
about. Please apologize if something already exists, but I don't know:
In HP-UX 11.31 you can print scan times
I'm running an iscsi root partition for a CentOS machine running a
2.6.18-53 kernel. Every couple of days I get the error:
connection1:0 detected conn error (1011)
session1: session recovery timed out after 400 sec
I compiled the open-iscsi 2.0-871 user tools and kernel modules from
source
On 07/13/2010 01:41 PM, Sean S wrote:
I'm running an iscsi root partition for a CentOS machine running a
2.6.18-53 kernel. Every couple of days I get the error:
connection1:0 detected conn error (1011)
session1: session recovery timed out after 400 sec
Is there anything more to the log
disconnect the ethernet from the initiator
while running, all I/O access is correctly paused without returning I/
O errors. If I then reconnect before the 400s is up things go back to
normal. I don't however see the detected conn error (1011) message
in this situation however. Not sure if that really
this with SLES10 SP2 x86_64 on the same setup.
Dec 7 18:42:05 cdc-r710s1 kernel: connection2:0: detected conn error
(1011)
Dec 7 18:42:06 cdc-r710s1 iscsid: connection2:0 is operational after
recovery (1 attempts)
Dec 7 18:42:06 cdc-r710s1 iscsid: Kernel reported iSCSI connection
2:0
avora wrote:
With SLES10 SP3 x86_64,
as soon as I start the second iscsi session2, I am very frequently
getting the connection errors/
I do not see this with SLES10 SP2 x86_64 on the same setup.
Dec 7 18:42:05 cdc-r710s1 kernel: connection2:0: detected conn error
(1011)
Dec 7 18:42:06
:15:13 cdc-r710s3 kernel: connection2:0: detected conn error (1011)
Dec 14 11:15:13 cdc-r710s3 iscsid: connection2:0 is operational after
recovery (1 attempts)
Dec 14 11:15:13 cdc-r710s3 iscsid: Kernel reported iSCSI connection 2:0 error
(1011) state (3)
Dec 14 11:15:14 cdc-r710s3 kernel
) copied, 0.177076 seconds, 28.9 MB/s
dd: reading `/dev/sdaa8': Input/output error
2976+0 records in
2976+0 records out
Dec 14 11:15:12 cdc-r710s3 iscsid: Kernel reported iSCSI connection 1:0 error
(1011) state (3)
Dec 14 11:15:13 cdc-r710s3 kernel: connection2:0: detected conn error (1011)
Dec
Sorry, I do not see an upload option for me even after (signing-in).
How to upload ?
--- On Thu, 12/10/09, Mike Christie micha...@cs.wisc.edu wrote:
From: Mike Christie micha...@cs.wisc.edu
Subject: Re: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011)
To: open-iscsi
Is CHAP configured on the array?
-Original Message-
From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
On Behalf Of Mike Christie
Sent: Wednesday, December 09, 2009 9:54 PM
To: open-iscsi@googlegroups.com
Subject: Re: SLES10 SP3 x86_64 - connection2:0: detected conn
Yes Mike, the recovery message is seen right away.
Dec 7 18:42:06 cdc-r710s1 iscsid: connection2:0 is operational after
recovery (1 attempts)
'conn error' and 'recovery' are seen one after the other, continuosly.
On Dec 10, 8:04 am, Mike Christie micha...@cs.wisc.edu wrote:
avora wrote:
I
There is no CHAP configured on the array.
--- On Thu, 12/10/09, berthiaume_wa...@emc.com berthiaume_wa...@emc.com wrote:
From: berthiaume_wa...@emc.com berthiaume_wa...@emc.com
Subject: RE: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011)
To: open-iscsi@googlegroups.com
Date
avora wrote:
Yes Mike, the recovery message is seen right away.
Dec 7 18:42:06 cdc-r710s1 iscsid: connection2:0 is operational after
recovery (1 attempts)
'conn error' and 'recovery' are seen one after the other, continuosly.
Do you have other initiators connected to the target?
Can
Session State: REPOEN
--- On Thu, 12/10/09, Mike Christie micha...@cs.wisc.edu wrote:
From: Mike Christie micha...@cs.wisc.edu
Subject: Re: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011)
To: open-iscsi@googlegroups.com
Date: Thursday, December 10, 2009, 11:22 PM
avora wrote
Anuarg Vora wrote:
I did sent the ethereal trace yesterday.
I am not sure why it didn't reach, is there any place I can upload it ?
http://groups-beta.google.com/group/open-iscsi/files
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to
I do not see ping/nop timeout message in the logs
(probably that's why changing the noop timeouts did not work).
Simply starting the session does not cause these errors.
On starting the second session, I start a daemon
that does SCSI commands like INQUIRY on all the paths.
After that I see these
I got a similar issue while browsing
http://groups.google.com/group/open-iscsi/browse_thread/thread/3c9c37903e40cd6f
I wanted to enable logging as mentioned in above link.
echo 1 /sys/module/libiscsi/parameters/debug_libiscsi_conn
echo 1
With SLES10 SP3 x86_64,
as soon as I start the second iscsi session2, I am very frequently
getting the connection errors/
I do not see this with SLES10 SP2 x86_64 on the same setup.
Dec 7 18:42:05 cdc-r710s1 kernel: connection2:0: detected conn error
(1011)
Dec 7 18:42:06 cdc-r710s1 iscsid
avora wrote:
With SLES10 SP3 x86_64,
as soon as I start the second iscsi session2, I am very frequently
getting the connection errors/
I do not see this with SLES10 SP2 x86_64 on the same setup.
Dec 7 18:42:05 cdc-r710s1 kernel: connection2:0: detected conn error
(1011)
Dec 7 18:42:06
On 11/10/09 11:39 AM, Mike Christie micha...@cs.wisc.edu wrote:
What version of open-iscsi were you using and what kernel, and were you
using the iscsi kernel modules with open-iscsi.org tarball or from the
kernel?
iscsi-initiator-utils-6.2.0.871-0.10.el5
kernel-2.6.18-164.2.1.el5
RedHat
Matthew Dickinson wrote:
On 11/10/09 11:39 AM, Mike Christie micha...@cs.wisc.edu wrote:
What version of open-iscsi were you using and what kernel, and were you
using the iscsi kernel modules with open-iscsi.org tarball or from the
kernel?
iscsi-initiator-utils-6.2.0.871-0.10.el5
sorry... wrong information. Here is the correct information. I was doing some
testing in VMWare Fusion VM's for a presentation that I'm giving. The
storage server is CentOS 5.3, which dishes out IETD targets for my OVM
servers. The OVM 2.2 environment is as follows:
[r...@ovm1 ~]# uname
Hoot, Joseph wrote:
I've had about 3 threads of dt (kicking off a bit randomly) on (3) separate
volumes for over a week and haven't had a single disconnect yet. I am
currently using whatever rpm is distributed with Oracle VM v2.2. I know for
sure that they have included the 871 base,
[r...@storage ~]# uname -r
2.6.18-164.el5
[r...@storage ~]# rpm -qa | grep iscsi
iscsi-initiator-utils-6.2.0.868-0.18.el5_3.1
[r...@storage ~]#
On Nov 10, 2009, at 12:17 PM, Mike Christie wrote:
Hoot, Joseph wrote:
I've had about 3 threads of dt (kicking off a bit randomly) on (3) separate
: detected conn error (1011)
Nov 10 09:08:05 backup iscsid: Kernel reported iSCSI connection 12:0 error
(1011) state (3)
Nov 10 09:08:08 backup iscsid: connection12:0 is operational after recovery
(1 attempts)
Nov 10 09:09:43 backup kernel: connection11:0: detected conn error (1011)
Nov 10 09
Hoot, Joseph wrote:
[r...@storage ~]# uname -r
2.6.18-164.el5
[r...@storage ~]# rpm -qa | grep iscsi
iscsi-initiator-utils-6.2.0.868-0.18.el5_3.1
[r...@storage ~]#
Weird.
Is 2.6.18-164.el5 the kernel being used in the virtual machine/DonU? Is
that where you are using iscsi? It looks
El 06/11/09 14:10, mdaitc escribió:
Hi mdaitc,
I’m seeing similar TCP “weirdness” as the other posts mention as well
as the below errors.
(..)
Nov 2 08:15:14 backup kernel: connection33:0: detected conn error
The performance isn’t what I’d expect:
(..)
What happens if you disable TCP
What version of OiS are you using? I had lots of weirdness and the
same types of disconnects to our Dell EqualLogic when we were
(actually still are in production) using 868 code. I'm now using open-
iscsi-871 code plus a sendwait patch and haven' had the issue. I've
now been slamming
4 05:12:14 backup kernel: connection22:0: ping timeout of 5 secs
expired, recv timeout 5, last rx 4321648393, last ping 4321653393, now
4321658393
Nov 4 05:12:14 backup kernel: connection22:0: detected conn error (1011)
Nov 4 05:12:21 backup iscsid: connection22:0 is operational after
Hoot, Joseph wrote:
What version of OiS are you using? I had lots of weirdness and the
same types of disconnects to our Dell EqualLogic when we were
(actually still are in production) using 868 code. I'm now using open-
iscsi-871 code plus a sendwait patch and haven' had the issue.
it was for OiS 871 code prior to RHEL 5.4 release (not sure if the
release include it or not). I'm not sure who came up with it. I was
working with Don Williams from Dell EqualLogic. He got ahold of it
somehow. I applied it and it seemed to improve things.
On Nov 9, 2009, at 2:31 PM,
Hoot, Joseph wrote:
it was for OiS 871 code prior to RHEL 5.4 release (not sure if the
release include it or not). I'm not sure who came up with it. I was
working with Don Williams from Dell EqualLogic. He got ahold of it
somehow. I applied it and it seemed to improve things.
Ah
I've had about 3 threads of dt (kicking off a bit randomly) on (3) separate
volumes for over a week and haven't had a single disconnect yet. I am
currently using whatever rpm is distributed with Oracle VM v2.2. I know for
sure that they have included the 871 base, plus I believe at least a
El 03/11/09 0:52, Mike Christie escribió:
Dear Mike,
You can turn off ping/nops by setting
node.conn[0].timeo.noop_out_interval = 0
node.conn[0].timeo.noop_out_timeout = 0
(set that in iscsid.conf then rediscovery the target or run iscsiadm -m
node -T your_target -o update -n
-17 kernel: ping timeout of 5 secs expired, last rx
408250499, last ping 408249467, now 408254467
Nov 2 18:34:02 vz-17 kernel: connection1:0: iscsi: detected conn
error (1011)
Nov 2 18:34:03 vz-17 iscsid: Kernel reported iSCSI connection 1:0
error (1011) state (3)
Nov 2 18:34:07 vz-17 iscsid
this:
===
Nov 2 18:34:02 vz-17 kernel: ping timeout of 5 secs expired, last rx
408250499, last ping 408249467, now 408254467
Nov 2 18:34:02 vz-17 kernel: connection1:0: iscsi: detected conn
error (1011)
Nov 2 18:34:03 vz-17 iscsid: Kernel reported iSCSI connection 1:0
error (1011
logs this:
===
Nov 2 18:34:02 vz-17 kernel: ping timeout of 5 secs expired, last rx
408250499, last ping 408249467, now 408254467
Nov 2 18:34:02 vz-17 kernel: connection1:0: iscsi: detected conn
error (1011)
Nov 2 18:34:03 vz-17 iscsid
Loading iSCSI transport class v2.0-870.
iscsi: registered transport (tcp)
iscsi: registered transport (iser)
scsi3 : iSCSI Initiator over TCP/IP
connection1:0: detected conn error (1011)
session1: host reset succeeded
connection1:0: detected conn error (1011)
session1: host reset succeeded
scsi
in at the iscsi level ok.
I am not sure why this would happen. Let me do some digging. I think
this might have come up before, but I did not see it.
connection1:0: detected conn error (1011)
session1: host reset succeeded
scsi 3:0:0:0: Device offlined - not ready after error recovery
#iscsiadm
session
tcp: [1] 10.52.145.121:3260,2 iqn.1999-02.com.nexsan:p1:sataboy:
028a2347
Loading iSCSI transport class v2.0-870.
iscsi: registered transport (tcp)
iscsi: registered transport (iser)
scsi3 : iSCSI Initiator over TCP/IP
connection1:0: detected conn error (1011)
session1: host
All sorted. Definitely running only open-iscsi now.
Still broken though
Loading iSCSI transport class v2.0-870.
iscsi: registered transport (tcp)
iscsi: registered transport (iser)
scsi6 : iSCSI Initiator over TCP/IP
connection1:0: detected conn error (1011)
session1: host reset succeeded
?
#iscsiadm -m session
tcp: [1] 10.52.145.121:3260,2 iqn.1999-02.com.nexsan:p1:sataboy:
028a2347
Loading iSCSI transport class v2.0-870.
iscsi: registered transport (tcp)
iscsi: registered transport (iser)
scsi3 : iSCSI Initiator over TCP/IP
connection1:0: detected conn error (1011)
session1
/IP
connection1:0: detected conn error (1011)
session1: host reset succeeded
connection1:0: detected conn error (1011)
session1: host reset succeeded
scsi 6:0:0:0: Device offlined - not ready after error recovery
Can you get a ethereal/wireshark trace?
On May 8, 5:08 pm, Mike
conn error (1011)
session1: host reset succeeded
connection1:0: detected conn error (1011)
session1: host reset succeeded
scsi 6:0:0:0: Device offlined - not ready after error recovery
Can you get a ethereal/wireshark trace?
On May 8, 5:08 pm, Mike Christie micha...@cs.wisc.edu
: registered transport (tcp)
iscsi: registered transport (iser)
scsi6 : iSCSI Initiator over TCP/IP
connection1:0: detected conn error (1011)
session1: host reset succeeded
connection1:0: detected conn error (1011)
session1: host reset succeeded
scsi 6:0:0:0: Device offlined - not ready after error
Konrad Rzeszutek schrieb:
On Thu, Apr 17, 2008 at 06:07:12AM -0400, Konrad Rzeszutek wrote:
It looks like the network is off but the session is still running. We
eventually get to the kernel shutoff here. Is your init script getting
run? If not then run it. If you left the session on on
Synchronizing SCSI cache for disk happens because:
- iSCSI sessions were not properly disconnected, and
Correct.
- they can't be properly disconnected any more, because the network is
already disabled.
Kind of. There is a kernel timer that gets activated during the logout sequence
that
: connection4:0: detected conn
error (1011)
Apr 23 12:32:42 virtualserv1 iscsid: connection4:0 is operational now
Apr 23 12:32:43 virtualserv1 iscsid: Kernel reported iSCSI connection
4:0 error (1011) state (3)
Apr 23 12:32:46 virtualserv1 kernel: session4: host reset succeeded
Apr 23 12:32
Konrad Rzeszutek wrote:
Firstly, I haven't dug in this yet but this is more of a call:
have-you-seen-this-too?
This is probably on the list 20 times :)
When I reboot the machine without logging off from iSCSI targets I can
hang the reboot sequence. This is with 869-rc4 userspace, SLES 10
It looks like the network is off but the session is still running. We
eventually get to the kernel shutoff here. Is your init script getting
run? If not then run it. If you left the session on on purpose then you
cannot turn the network off because the scsi layer will want to do its
77 matches
Mail list logo
