Hallo,
uns fiel gestern ein Controller am SAN-Storage aus, und open-iscsi auf SLES10
SP3 (open-iscsi-2.0.868-0.6.11) erzeugte _sehr_ viele (419869 Einträge in
wenigen Stunden) Fehlermeldungen in Syslog. Gat Novell Bestrebungen, diese zu
drosseln? Beispiel:
Sep 7 16:08:23 hostname kernel:
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.
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. The underlying
: 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,
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
On 08/04/2010 04:12 PM, Goncalo Gomes wrote:
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 storage for these VMs is
iSCSI based via open-iscsi 2.0.870-26.6.1 and a DELL equallogic array.
Whenever the
On 23 Apr, 20:29, Mike Christie [EMAIL PROTECTED] wrote:
DaMn wrote:
Hi,
despite the Subject, i've not found a solution to my problem in others
threads.
I'm having trouble connecting a target with two LUN:
# iscsiadm -m discovery -t st -p 192.168.29.13
puts out:
14 matches
Mail list logo
