From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?BERTRAND_Jo=EBl?= Subject: Re: [BUG] Raid1/5 over iSCSI trouble Date: Fri, 19 Oct 2007 23:06:46 +0200 Message-ID: <47191C66.309@systella.fr> References: <4714BB92.7040701@systella.fr> <47161CE3.80909@systella.fr> <47181CB2.1060602@tmr.com> <471864F8.9010209@systella.fr><1192809103.30976.11.camel@dwillia2-linux.ch.intel.com><4718DE66.8000905@tmr.com> <471916B5.6080709@systella.fr> <47191855.4020402@systella.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iscsitarget-devel-bounces@lists.sourceforge.net Errors-To: iscsitarget-devel-bounces@lists.sourceforge.net To: "Ross S. W. Walker" Cc: linux-raid@vger.kernel.org, sparclinux@vger.kernel.org, Dan Williams , iscsitarget-devel@lists.sourceforge.net, Bill Davidsen List-Id: linux-raid.ids Ross S. W. Walker wrote: > BERTRAND Jo=EBl wrote: >> BERTRAND Jo=EBl wrote: >>> Bill Davidsen wrote: >>>> Dan Williams wrote: >>>>> On Fri, 2007-10-19 at 01:04 -0700, BERTRAND Jo=EBl wrote: >>>>> = >>>>>> I run for 12 hours some dd's (read and write in nullio) >>>>>> between >>>>>> initiator and target without any disconnection. Thus = >> iSCSI code seems >>>>>> to >>>>>> be robust. Both initiator and target are alone on a = >> single gigabit >>>>>> ethernet link (without any switch). I'm investigating... >>>>>> = >>>>> Can you reproduce on 2.6.22? >>>>> >>>>> Also, I do not think this is the cause of your failure, = >> but you have >>>>> CONFIG_DMA_ENGINE=3Dy in your config. Setting this to 'n' = >> will compile >>>>> out the unneeded checks for offload engines in async_memcpy and >>>>> async_xor. >>>> Given that offload engines are far less tested code, I = >> think this is a = >>>> very good thing to try! >>> I'm trying wihtout CONFIG_DMA_ENGINE=3Dy. istd1 only uses = >> 40% of one = >>> CPU when I rebuild my raid1 array. 1% of this array was now = >>> resynchronized without any hang. >>> >>> Root gershwin:[/usr/scripts] > cat /proc/mdstat >>> Personalities : [raid1] [raid6] [raid5] [raid4] >>> md7 : active raid1 sdi1[2] md_d0p1[0] >>> 1464725632 blocks [2/1] [U_] >>> [>....................] recovery =3D 1.0% = >> (15705536/1464725632) = >>> finish=3D1103.9min speed=3D21875K/sec >> Same result... >> >> connection2:0: iscsi: detected conn error (1011) >> = >> session2: iscsi: session recovery timed out after 120 secs >> sd 4:0:0:0: scsi: Device offlined - not ready after error recovery >> sd 4:0:0:0: scsi: Device offlined - not ready after error recovery >> sd 4:0:0:0: scsi: Device offlined - not ready after error recovery >> sd 4:0:0:0: scsi: Device offlined - not ready after error recovery >> sd 4:0:0:0: scsi: Device offlined - not ready after error recovery >> sd 4:0:0:0: scsi: Device offlined - not ready after error recovery >> sd 4:0:0:0: scsi: Device offlined - not ready after error recovery > = > I am unsure why you would want to setup an iSCSI RAID1, but before > doing so I would try to verify that each independant iSCSI session > is bullet proof. I use one and only one iSCSI session. Raid1 array is built between a = local and iSCSI volume. JKB ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?BERTRAND_Jo=EBl?= Date: Fri, 19 Oct 2007 21:06:46 +0000 Subject: Re: [Iscsitarget-devel] [BUG] Raid1/5 over iSCSI trouble Message-Id: <47191C66.309@systella.fr> List-Id: References: <4714BB92.7040701@systella.fr> <47161CE3.80909@systella.fr> <47181CB2.1060602@tmr.com> <471864F8.9010209@systella.fr><1192809103.30976.11.camel@dwillia2-linux.ch.intel.com><4718DE66.8000905@tmr.com> <471916B5.6080709@systella.fr> <47191855.4020402@systella.fr> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: "Ross S. W. Walker" Cc: linux-raid@vger.kernel.org, sparclinux@vger.kernel.org, Dan Williams , iscsitarget-devel@lists.sourceforge.net, Bill Davidsen Ross S. W. Walker wrote: > BERTRAND Jo=EBl wrote: >> BERTRAND Jo=EBl wrote: >>> Bill Davidsen wrote: >>>> Dan Williams wrote: >>>>> On Fri, 2007-10-19 at 01:04 -0700, BERTRAND Jo=EBl wrote: >>>>> =20 >>>>>> I run for 12 hours some dd's (read and write in nullio) >>>>>> between >>>>>> initiator and target without any disconnection. Thus=20 >> iSCSI code seems >>>>>> to >>>>>> be robust. Both initiator and target are alone on a=20 >> single gigabit >>>>>> ethernet link (without any switch). I'm investigating... >>>>>> =20 >>>>> Can you reproduce on 2.6.22? >>>>> >>>>> Also, I do not think this is the cause of your failure,=20 >> but you have >>>>> CONFIG_DMA_ENGINE=3Dy in your config. Setting this to 'n'=20 >> will compile >>>>> out the unneeded checks for offload engines in async_memcpy and >>>>> async_xor. >>>> Given that offload engines are far less tested code, I=20 >> think this is a=20 >>>> very good thing to try! >>> I'm trying wihtout CONFIG_DMA_ENGINE=3Dy. istd1 only uses=20 >> 40% of one=20 >>> CPU when I rebuild my raid1 array. 1% of this array was now=20 >>> resynchronized without any hang. >>> >>> Root gershwin:[/usr/scripts] > cat /proc/mdstat >>> Personalities : [raid1] [raid6] [raid5] [raid4] >>> md7 : active raid1 sdi1[2] md_d0p1[0] >>> 1464725632 blocks [2/1] [U_] >>> [>....................] recovery =3D 1.0%=20 >> (15705536/1464725632)=20 >>> finish=1103.9min speed!875K/sec >> Same result... >> >> connection2:0: iscsi: detected conn error (1011) >> =20 >> session2: iscsi: session recovery timed out after 120 secs >> sd 4:0:0:0: scsi: Device offlined - not ready after error recovery >> sd 4:0:0:0: scsi: Device offlined - not ready after error recovery >> sd 4:0:0:0: scsi: Device offlined - not ready after error recovery >> sd 4:0:0:0: scsi: Device offlined - not ready after error recovery >> sd 4:0:0:0: scsi: Device offlined - not ready after error recovery >> sd 4:0:0:0: scsi: Device offlined - not ready after error recovery >> sd 4:0:0:0: scsi: Device offlined - not ready after error recovery >=20 > I am unsure why you would want to setup an iSCSI RAID1, but before > doing so I would try to verify that each independant iSCSI session > is bullet proof. I use one and only one iSCSI session. Raid1 array is built between a=20 local and iSCSI volume. JKB