[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47305288.8020307@systella.fr>
Date: Tue, 06 Nov 2007 12:39:52 +0100
From: BERTRAND Joël <joel.bertrand@...tella.fr>
To: Justin Piszcz <jpiszcz@...idpixels.com>
CC: Dan Williams <dan.j.williams@...el.com>,
Neil Brown <neilb@...e.de>, linux-kernel@...r.kernel.org,
linux-raid@...r.kernel.org
Subject: Re: 2.6.23.1: mdadm/raid5 hung/d-state
Justin Piszcz wrote:
>
>
> On Tue, 6 Nov 2007, BERTRAND Joël wrote:
>
>> Done. Here is obtained ouput :
>>
>> [ 1265.899068] check 4: state 0x6 toread 0000000000000000 read
>> 0000000000000000 write fffff800fdd4e360 written 0000000000000000
>> [ 1265.941328] check 3: state 0x1 toread 0000000000000000 read
>> 0000000000000000 write 0000000000000000 written 0000000000000000
>> [ 1265.972129] check 2: state 0x1 toread 0000000000000000 read
>> 0000000000000000 write 0000000000000000 written 0000000000000000
>>
>>
>> For information, after crash, I have :
>>
>> Root poulenc:[/sys/block] > cat /proc/mdstat
>> Personalities : [raid1] [raid6] [raid5] [raid4]
>> md_d0 : active raid5 sdc1[0] sdh1[5] sdg1[4] sdf1[3] sde1[2] sdd1[1]
>> 1464725760 blocks level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
>>
>> Regards,
>>
>> JKB
>
> After the crash it is not 'resyncing' ?
No, it isn't...
JKB
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists