From: Joshua Kinard <kumba@gentoo.org>
To: linux-raid@vger.kernel.org
Subject: Problem w/ commit ac8fa4196d20 on older, slower hardware
Date: Mon, 5 Oct 2015 03:41:39 -0400 [thread overview]
Message-ID: <561229B3.4050101@gentoo.org> (raw)
Per commit ac8fa4196d20:
> md: allow resync to go faster when there is competing IO.
>
> When md notices non-sync IO happening while it is trying to resync (or
> reshape or recover) it slows down to the set minimum.
>
> The default minimum might have made sense many years ago but the drives have
> become faster. Changing the default to match the times isn't really a long
> term solution.
This holds true for modern hardware, but this commit is causing problems on
older hardware, like SGI MIPS platforms, that use mdraid. Namely, while trying
to chase down an unrelated hardlock bug on an Onyx2, one of the arrays got out
of sync, so on the next reboot, mdraid's attempt to resync at full speed
absolutely murdered interactivity. It took close to 30mins for the system to
finally reach the login prompt.
Revert this patch was working to mitigate the problem at first, but it appears
that in recent kernels, this is no longer the case, and reverting this commit
has no noticeable effect anymore. I assume I'd have to hunt down newer commits
to revert, but it's probably saner to just highlight the problem and test any
proposed solutions.
Is there some way to resolve this in such a way that old hardware maintains
some level of interactivity during a resync, but that won't inconvenience the
more modern systems?
http://git.linux-mips.org/cgit/ralf/linux.git/commit/?id=ac8fa4196d20
Thanks!,
--J
next reply other threads:[~2015-10-05 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 7:41 Joshua Kinard [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-09 0:13 Problem w/ commit ac8fa4196d20 on older, slower hardware Neil Brown
2015-11-12 22:28 ` Joshua Kinard
2015-11-13 0:03 ` Andreas Klauer
2015-12-21 0:43 ` NeilBrown
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=561229B3.4050101@gentoo.org \
--to=kumba@gentoo.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 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.