From: Kevin Ross <kevin@familyross.net>
To: Phil Turmel <philip@turmel.org>
Cc: linux-kernel@vger.kernel.org, linux-raid <linux-raid@vger.kernel.org>
Subject: Re: RAID extremely slow
Date: Wed, 25 Jul 2012 18:55:18 -0700 [thread overview]
Message-ID: <5010A386.4080209@familyross.net> (raw)
In-Reply-To: <501096C3.5060700@turmel.org>
Thank you very much for taking the time to look into this.
On 07/25/2012 06:00 PM, Phil Turmel wrote:
> Piles of small reads scattered across multiple drives, and a
> concentration of queued writes to /dev/sda. What's on /dev/sda?
> It's not a member of the raid, so it must be some other system task
> involved.
/dev/sda1 is the root filesystem. The writes were most likely by MySQL,
but I would have to run iotop to be sure.
> [ The output of "lsdrv" [1] might be useful here, along with
> "mdadm -D /dev/md0" and "mdadm -E /dev/[b-j]" ]
Here you go: http://pastebin.ca/2174740
> MythTV is trying to flush recorded video to disk, I presume. Sync is
> known to cause stalls--a great deal of work is on-going to improve
> this. How old is this kernel?
After rebooting, MythTV is currently recording two shows, and the resync
is running at full speed.
# 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 = 9.3% (91363840/976758784)
finish=1434.3min speed=10287K/sec
unused devices: <none>
atop shows the avio of all the drives to be less than 1ms, where before
they were much higher. It will run for a couple days under load just
fine, and then it will come to a halt.
It's a 3.2.21 kernel. I'm running Debian Testing, and the exact Debian
package version is:
ii linux-image-3.2.0-3-686-pae
3.2.21-3 Linux 3.2 for modern PCs
>
>> [51000.672258] [<c12c409f>] ? sysenter_do_call+0x12/0x28
>> [51000.672261] [<c12b0000>] ? quirk_usb_early_handoff+0x4a9/0x522
>>
>> Here is some other possibly relevant info:
>>
>> # 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 = 51.3% (501954432/976758784)
>> finish=28755.6min speed=275K/sec
> Is this resync a weekly check, or did something else trigger it?
This is not a scheduled check. It was triggered by, I believe, an
unclean shutdown. An unclean shutdown will trigger a resync. I don't
think it used to do this, but I could be remembering wrong.
>
>> 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.
>> # cat /proc/sys/dev/raid/speed_limit_max
>> 200000
>>
>> Thanks in advance!
>> -- Kevin
> HTH,
>
> Phil
>
> [1] http://github.com/pturmel/lsdrv
>
Thanks!
-- Kevin
next prev parent reply other threads:[~2012-07-26 1:55 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 [this message]
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
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=5010A386.4080209@familyross.net \
--to=kevin@familyross.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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