Re: [BUG] Raid5 trouble

["BERTRAND Joël" <joel.bertrand@systella.fr>]

Bill Davidsen wrote:
> Dan Williams wrote:
>> On Fri, 2007-10-19 at 01:04 -0700, BERTRAND Joël 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=y 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=y. 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 =  1.0% (15705536/1464725632) 
finish=1103.9min speed=21875K/sec

	Regards,

	JKB
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html