From: "Jianpeng Ma" <majianpeng@gmail.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Re: [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time
Date: Wed, 26 Sep 2012 17:14:31 +0800 [thread overview]
Message-ID: <2012092617142881237818@gmail.com> (raw)
In-Reply-To: 20120926124348.3190990c@notabene.brown
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
On 2012-09-26 10:43 NeilBrown <neilb@suse.de> Wrote:
>On Tue, 25 Sep 2012 17:29:12 +1000 NeilBrown <neilb@suse.de> wrote:
>
>> On Fri, 21 Sep 2012 10:24:45 +0800 "Jianpeng Ma" <majianpeng@gmail.com> wrote:
>
>> > Hi,
>> > i wrote a shell-script can reproduct this bug.
>> > Note: mdadm -V
>> > mdadm - v3.3-pre - Unreleased
>> >
>...
>
>> Thanks a lot!
>> I'll try this out and see what I find.
>
>I've been running this script (with the mentioned version of mdadm) and
>nothing has gone wrong.
>The 'dd' keeps reporting read errors of course, as does the kernel, but not
>crash or freeze or anything.
>
>What exactly happens when you run it? Do you get a kernel stack trace at all?
>Can you post logs showing where it goes wrong?
>
>Thanks,
>NeilBrown
Hi:
The attachement is the kerne log which enabling dynamic_debug.
I hope you can get some useful infos from this log.If can't,can you suggest what place to add debug?
Thanks!
[-- Attachment #2: kern.rar --]
[-- Type: application/octet-stream, Size: 34412 bytes --]
prev parent reply other threads:[~2012-09-26 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 2:20 [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time Jianpeng Ma
2012-09-20 2:51 ` NeilBrown
2012-09-20 3:04 ` Jianpeng Ma
2012-09-20 3:24 ` NeilBrown
2012-09-20 6:04 ` Jianpeng Ma
2012-09-21 2:24 ` Jianpeng Ma
2012-09-25 7:29 ` NeilBrown
2012-09-26 2:43 ` NeilBrown
2012-09-26 4:09 ` Jianpeng Ma
2012-09-26 9:14 ` Jianpeng Ma [this message]
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=2012092617142881237818@gmail.com \
--to=majianpeng@gmail.com \
--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.