From: Du Jun <dujun@perabytes.com>
To: linux-raid@vger.kernel.org
Subject: raid related kernel hang in 2.6.36
Date: Wed, 24 Nov 2010 21:48:20 +0800 [thread overview]
Message-ID: <4CED17A4.7050604@perabytes.com> (raw)
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
next reply other threads:[~2010-11-24 13:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 13:48 Du Jun [this message]
2010-11-24 14:19 ` raid related kernel hang in 2.6.36 Mathias Burén
2010-11-24 14:34 ` Du Jun
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=4CED17A4.7050604@perabytes.com \
--to=dujun@perabytes.com \
--cc=linux-raid@vger.kernel.org \
/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).