From: Du Jun <dujun@perabytes.com>
To: "Mathias Burén" <mathias.buren@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid related kernel hang in 2.6.36
Date: Wed, 24 Nov 2010 22:34:21 +0800 [thread overview]
Message-ID: <4CED226D.6090602@perabytes.com> (raw)
In-Reply-To: <AANLkTinfbPDQhmKRVibUv+Rm50wDkGizeYLGXQqY_xOu@mail.gmail.com>
Their's no dmesg information at all before the hang. The system just
hangs suddenly without any kernel printk or oops.
mdadm version is debian lenny version 2.6.7.2-3
I will get mdadm -E & mdadm -D informations tomorrow but I doubt they
are useful.
Johnson
on 2010/11/24 22:19, Mathias Burén wrote:
> Hi,
>
> I suppose a few logs would be interesting. (dmesg, mdadm -E (hdds),
> mdadm -D md10, zcat /proc/config.gz, mdadm version)
>
> Regards,
> // Mathias
>
> 2010/11/24 Du Jun<dujun@perabytes.com>:
>
>> Hi,
>> We just quick tested the raid stability under the vanilla 2.6.36 kernel
>> and got an unstable result.
>>
>> first, we create a raid5 array using 16 sata disks:
>>
>> mdadm -C /dev/md10 -l 5 -n 16 /dev/sd[b-q]
>>
>> then use dd to stress the io:
>>
>> dd if=/dev/zero of=/dev/md10 bs=1M
>>
>> After a while, usually several minutes, the system hangs. It looks like
>> some kind of kernel deadlock. ping to this machine could get timely
>> response, however, any other process just hangs.
>>
>> It is easily reproducible and everytime the test result is a system hang.
>>
>> Johnson
>>
>> --
>> 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
>>
>>
> --
> 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
>
>
>
--
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
next prev parent reply other threads:[~2010-11-24 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 13:48 raid related kernel hang in 2.6.36 Du Jun
2010-11-24 14:19 ` Mathias Burén
2010-11-24 14:34 ` Du Jun [this message]
2010-11-24 20:01 ` Neil Brown
2010-11-24 21:15 ` Carlos Carvalho
2010-11-25 3:12 ` dujun
2011-02-10 16:28 ` Iordan Iordanov
2011-02-11 15:52 ` Iordan Iordanov
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=4CED226D.6090602@perabytes.com \
--to=dujun@perabytes.com \
--cc=linux-raid@vger.kernel.org \
--cc=mathias.buren@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).