From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Neil Brown <neilb@suse.de>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: 2.6.23.1: mdadm/raid5 hung/d-state
Date: Tue, 06 Nov 2007 12:39:52 +0100 [thread overview]
Message-ID: <47305288.8020307@systella.fr> (raw)
In-Reply-To: <Pine.LNX.4.64.0711060628450.3010@p34.internal.lan>
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-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Neil Brown <neilb@suse.de>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: 2.6.23.1: mdadm/raid5 hung/d-state
Date: Tue, 06 Nov 2007 12:39:52 +0100 [thread overview]
Message-ID: <47305288.8020307@systella.fr> (raw)
In-Reply-To: <Pine.LNX.4.64.0711060628450.3010@p34.internal.lan>
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
next prev parent reply other threads:[~2007-11-06 11:39 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 12:03 2.6.23.1: mdadm/raid5 hung/d-state Justin Piszcz
2007-11-04 12:39 ` 2.6.23.1: mdadm/raid5 hung/d-state (md3_raid5 stuck in endless loop?) Justin Piszcz
2007-11-04 12:48 ` 2.6.23.1: mdadm/raid5 hung/d-state Michael Tokarev
2007-11-04 12:52 ` Justin Piszcz
2007-11-04 14:55 ` Michael Tokarev
2007-11-04 14:59 ` Justin Piszcz
2007-11-04 18:17 ` BERTRAND Joël
2007-11-04 21:40 ` David Greaves
2007-11-04 13:40 ` BERTRAND Joël
2007-11-04 13:42 ` Justin Piszcz
2007-11-04 21:49 ` Neil Brown
2007-11-04 21:51 ` Justin Piszcz
2007-11-05 18:35 ` Dan Williams
2007-11-05 18:35 ` Dan Williams
2007-11-05 18:35 ` Justin Piszcz
2007-11-06 0:19 ` Dan Williams
2007-11-06 10:19 ` BERTRAND Joël
2007-11-06 11:29 ` Justin Piszcz
2007-11-06 11:39 ` BERTRAND Joël [this message]
2007-11-06 11:39 ` BERTRAND Joël
2007-11-06 11:42 ` Justin Piszcz
2007-11-06 12:20 ` BERTRAND Joël
2007-11-06 12:20 ` BERTRAND Joël
2007-11-07 1:25 ` Dan Williams
2007-11-07 5:00 ` Jeff Lessem
2007-11-08 17:45 ` Bill Davidsen
2007-11-08 18:02 ` Dan Williams
2007-11-09 20:36 ` Jeff Lessem
2007-11-08 21:40 ` Carlos Carvalho
2007-11-09 9:14 ` Justin Piszcz
2007-11-09 14:09 ` Fabiano Silva
2007-11-07 11:20 ` BERTRAND Joël
2007-11-07 11:20 ` BERTRAND Joël
2007-11-06 23:18 ` Jeff Lessem
2007-11-05 8:36 ` BERTRAND Joël
2007-11-07 16:39 ` Chuck Ebbert
2007-11-07 16:39 ` Chuck Ebbert
2007-11-07 16:48 ` BERTRAND Joël
2007-11-07 16:48 ` BERTRAND Joël
2007-11-08 11:42 ` BERTRAND Joël
2007-11-08 11:42 ` BERTRAND Joël
2007-11-08 12:44 ` Justin Piszcz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47305288.8020307@systella.fr \
--to=joel.bertrand@systella.fr \
--cc=dan.j.williams@intel.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.