From: Nix <nix@esperi.org.uk>
To: linux-raid@vger.kernel.org
Subject: insane md check latencies with multiple devices on one disk
Date: Tue, 02 Jan 2018 11:05:03 +0000 [thread overview]
Message-ID: <87r2r8ed28.fsf@esperi.org.uk> (raw)
So I have a triplet of RAID arrays (md0 and md6) on 6x modern rotating
storage (read speeds for contiguous reads nearly 200MiB/s: much much
slower when seeking, naturally). There are three arrays on one set of
disks, md0 at the start and two md6 later on (one of them is backing a
bcache, the other is not). Most non-archival data is on the bcached
array.
A routine every-N-months RAID check of the md6 arrays has just kicked
in, and I'm being murdered by latencies: even writing this email is
painful due to massive blocking (latencytop shows routine 20s latencies,
which is just appalling).
The md device that's syncing right now is for archival storage: the one
for the OS and $HOME and the like is not syncing, and the sync speed
is sitting at the max for the disk, not dropping when user-requested I/O
takes place.
The problem, I think, is that while md realizes that all three devices
are on one disk for the purpose of serializing checks, it doesn't
realize that md devices sharing disks also implies that I/O to every
such device should reduce the sync speed of every md device syncing on
that disk, not just the one to which the I/O is directed. Not knowing
anything about that part of the code, I'm wondering how hard that would
be to add... I'll have a look. (This is obviously not urgent since I
can't improve performance for this check, since it would require a
reboot to do so :) I'll just knock down sync_speed_max for now and live
with that).
reply other threads:[~2018-01-02 11:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87r2r8ed28.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).