Hi Hannes,
I am seeing similar problems.
What kernel do you mean, that has fixes?
On Jan 13, 7:24 am, Hannes Reinecke h...@suse.de wrote:
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
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
-beta.google.com/group/open-iscsi/files
Regards,
Anurag
--- On Fri, 12/11/09, Anuarg Vora anurag_vo...@yahoo.com wrote:
From: Anuarg Vora anurag_vo...@yahoo.com
Subject: Re: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011)
To: open-iscsi@googlegroups.com
Date: Friday, December 11, 2009
...@yahoo.com wrote:
From: Anuarg Vora anurag_vo...@yahoo.com
Subject: Re: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011)
To: open-iscsi@googlegroups.com
Date: Friday, December 11, 2009, 12:22 AM
Sorry, I do not see an upload option
for me even after (signing-in).
How
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
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
14 matches
Mail list logo
