From: Martin Hamrle <martin.hamrle@nangu.tv>
To: linux-raid@vger.kernel.org
Subject: sw raid5 hungs on resync and high IO load, 2.6.32.23
Date: Wed, 27 Oct 2010 09:35:17 +0200 [thread overview]
Message-ID: <4CC7D635.6050000@nangu.tv> (raw)
Hi,
I'm having this issue on several boxes with several configuration.
One of them is a box with 8 drives attached to ARC-1160 in pass through
mode and build sw raid5 from these drives. There is also one drive to OS.
During resync or check and heavy IO load, process tscpd (tscpd is IO
load maker) hungs, the machine is still alive but there are many blocked
processes.
After tscpd hungs, IO load is generated only by resync. In traceback you
can see blocked processes (ps, htop cat) accessing tscpd cmdline in
proc. Some tscpd threads is blocked during writing files into fs on
raid5. Reading these files is also blocking, reading other files in
filesystem is fast as usual. This state takes 110 minutes. After that
all blocked processes continue their work.
I am not sure what is the reason of the end of the weird state. I think
the end was caused by starting copying kernel source into array.
Note that this is first time when hung processes wake up I never wait so
long.
I think that it is related to sw raid because I do not see this issue on
hw raid or on sw raid without resync.
kern.log contains initial "INFO: task collectd:2577 blocked for more
than 120 seconds"
and two dumps
echo w > /proc/sysrq-trigger
log is located http://files.nangu.tv/kernel/kern.log
Let me know if you need more info.
Martin
next reply other threads:[~2010-10-27 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 7:35 Martin Hamrle [this message]
2010-10-27 8:01 ` sw raid5 hungs on resync and high IO load, 2.6.32.23 Neil Brown
2010-10-27 10:48 ` Martin Hamrle
2010-11-15 1:51 ` Neil Brown
2010-10-27 8:50 ` Mikael Abrahamsson
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=4CC7D635.6050000@nangu.tv \
--to=martin.hamrle@nangu.tv \
--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 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.