From: david@lang.hm
To: Holger Kiehl <Holger.Kiehl@dwd.de>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-raid <linux-raid@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Raid reconstructing and process hanging in D state
Date: Fri, 16 Oct 2009 12:28:49 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0910161226170.22169@asgard.lang.hm> (raw)
In-Reply-To: <Pine.LNX.4.64.0910160840400.2463@praktifix.dwd.de>
On Fri, 16 Oct 2009, Holger Kiehl wrote:
> On Fri, 16 Oct 2009, Justin Piszcz wrote:
>> Hi,
>>
>> I have the same problem with mdadm/raid-1, if you do not limit the speed in
>> the speed_limit_min paramter, it will starve the I/O from all other
>> processes and result in the same problem you are having.
>>
> But in my case speed_limit_min was set to 1000 and speed_limit_max was 200000
> (ie. the default) and this still caused all process to hang in D-state. Only
> lowering speed_limit_max helped to make the system responsive again.
yep, MD raid will use every bit of disk bandwidth there is.
even worse, the speed_limit_* appears to be per-drive, not per array
(although the /proc/mdstat info is per array), so if you have lots of
drives on one controller card it will kill the system and still think that
it's not maxed out.
I did a 45 disk array hooked into two PCI slots and found that I needed to
set speed_limit_max _very_ low to avoid this sort of problem.
David Lang
>> But for me I'm not sure about the reconstruction-- this happens for me
>> during a raid verify/check.
>>
> This was also the case for me, during a raid verify/check.
>
> Holger
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2009-10-16 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 7:17 Holger Kiehl
2009-10-16 8:37 ` Justin Piszcz
2009-10-16 8:44 ` Holger Kiehl
2009-10-16 9:48 ` Justin Piszcz
2009-10-16 19:28 ` david [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=alpine.DEB.2.00.0910161226170.22169@asgard.lang.hm \
--to=david@lang.hm \
--cc=Holger.Kiehl@dwd.de \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®