From: Bill Davidsen <davidsen@tmr.com>
To: Kevin Ross <kevin@familyross.net>,
Linux RAID <linux-raid@vger.kernel.org>,
Linux Kernel mailing List <linux-kernel@vger.kernel.org>
Subject: Re: RAID extremely slow
Date: Fri, 27 Jul 2012 15:08:07 -0400 [thread overview]
Message-ID: <5012E717.9070808@tmr.com> (raw)
In-Reply-To: <5010CEFF.5030606@familyross.net>
Kevin Ross wrote:
>
>>>
>>>> unused devices:<none>
>>>>
>>>> # cat /proc/sys/dev/raid/speed_limit_min
>>>> 10000
>>> MD is unable to reach its minimum rebuild rate while other system
>>> activity is ongoing. You might want to lower this number to see if that
>>> gets you out of the stalls.
>>>
>>> Or temporarily shut down mythtv.
>>
>> I will try lowering those numbers next time this happens, which will probably
>> be within the next day or two. That's about how often this happens.
>
> Unfortunately, it has happened again, with speeds at near zero.
>
> # cat /proc/mdstat
> Personalities : [raid6] [raid5] [raid4]
> md0 : active raid6 sdh1[0] sdd1[9] sde1[10] sdb1[6] sdi1[7] sdc1[4] sdf1[3]
> sdg1[8] sdj1[1]
> 6837311488 blocks super 1.2 level 6, 512k chunk, algorithm 2 [9/9]
> [UUUUUUUUU]
> [=>...................] resync = 8.3% (81251712/976758784)
> finish=1057826.4min speed=14K/sec
>
> unused devices: <none>
>
> atop doesn't show ANY activity on the raid device or the individual drives.
> http://img687.imageshack.us/img687/2913/screenshotfrom201207252.png
>
> Also, I tried writing to a test file with the following command, and it hangs.
> I let it go for about 30 minutes, with no change.
>
> # dd if=/dev/zero of=test bs=1M count=1
>
> dmesg only reports hung tasks. It doesn't report any other problems. Here's my
> dmesg output:
> http://pastebin.ca/2174778
>
> I'm going to try rebooting into single user mode, and see if the rebuild
> succeeds without stalling.
>
Have you set the io scheduler to deadline on all members of the array? That's
kind of "job one" on older kernels.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2012-07-27 19:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 22:52 RAID extremely slow Kevin Ross
2012-07-26 1:00 ` Phil Turmel
2012-07-26 1:55 ` Kevin Ross
2012-07-26 2:09 ` CoolCold
2012-07-26 2:18 ` Kevin Ross
2012-07-26 5:00 ` Kevin Ross
2012-07-26 22:36 ` Kevin Ross
2012-07-27 19:08 ` Bill Davidsen [this message]
2012-07-27 21:45 ` Kevin Ross
2012-07-28 4:45 ` Grant Coady
2012-07-28 8:34 ` Kevin Ross
2012-08-01 3:16 ` Bill Davidsen
2012-07-27 2:15 ` David Dillow
2012-07-27 2:17 ` David Dillow
2012-07-27 2:17 ` Kevin Ross
2012-07-27 2:27 ` David Dillow
2012-07-27 2:53 ` Kevin Ross
2012-07-27 3:17 ` Kevin Ross
2012-08-17 21:55 ` Jan Engelhardt
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=5012E717.9070808@tmr.com \
--to=davidsen@tmr.com \
--cc=kevin@familyross.net \
--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