From: Tommy Apel Hansen <tommyapeldk@gmail.com>
To: Roman Mamedov <rm@romanrm.ru>
Cc: stan@hardwarefreak.com, tomas.hodek@volny.cz, linux-raid@vger.kernel.org
Subject: Re: raid1 read balance with write mostly
Date: Sat, 02 Feb 2013 23:16:23 +0100 [thread overview]
Message-ID: <1359843383.430.18.camel@workstation-home> (raw)
In-Reply-To: <20130203040758.5e2e7f3c@natsu>
On Sun, 2013-02-03 at 04:07 +0600, Roman Mamedov wrote:
> On Sat, 02 Feb 2013 15:52:12 -0600
> Stan Hoeppner <stan@hardwarefreak.com> wrote:
>
> > So under heavy read load, in this case we'd probably want the slow 3TB drive
> > to contribute to the workload.
>
> No, it should behave as documented.
>
> -W, --write-mostly
> subsequent devices listed in a --build, --create, or --add com‐
> mand will be flagged as 'write-mostly'. This is valid for RAID1
> only and means that the 'md' driver will avoid reading from
> these devices if at all possible.
^^^^^^^^^^^^^^^^^^^
I would assume that if the kernel thinks the SSD is starved for io (that
being the %util column in iostat) it would consider sending io to the
HDD. At least that would be what I would expect to happen, so if the SSD
reports wrong utilization numbers back or anything else involved in the
io processing the the behavior is as expected.
>
>
> if at all possible = if there is any other mirror still alive, do not read from
> this one.
>
> BTW I also run an SSD+HDD array, and after a brief testing today I did notice
> some reads from the HDD on reading from the array showing up in iostat. So I
> can confirm the bug.
>
/Tommy
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-02-02 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 17:38 raid1 read balance with write mostly tomas.hodek
2013-02-02 21:52 ` Stan Hoeppner
2013-02-02 22:07 ` Roman Mamedov
2013-02-02 22:16 ` Tommy Apel Hansen [this message]
2013-02-03 9:02 ` tomas.hodek
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=1359843383.430.18.camel@workstation-home \
--to=tommyapeldk@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=rm@romanrm.ru \
--cc=stan@hardwarefreak.com \
--cc=tomas.hodek@volny.cz \
/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).