Re: detected conn error (1011)

2010-08-06 Thread Hannes Reinecke
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 open-iscsi 2.0.870-26.6.1

RE: detected conn error (1011)

2010-08-06 Thread Goncalo Gomes
Hi Hannes, Would you be able to send me a unified patch containing the changes included in the test kernels so I can rebuild the drivers with them and update you today? For completeness, we are not running SLES, but rather the Citrix XenServer 5.6 release which is based off of the Linux 2.6.27

Re: detected conn error (1011)

2010-08-06 Thread Mike Christie
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

Re: detected conn error (1011)

2010-08-06 Thread Mike Christie
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, Qlog