From: NeilBrown <neilb@suse.de>
To: Rory Jaffe <rsjaffe@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Resync intermittently writes to spare drives, waking them up
Date: Mon, 18 Apr 2011 10:55:18 +1000 [thread overview]
Message-ID: <20110418105518.2ef04e47@notabene.brown> (raw)
In-Reply-To: <BANLkTikqAaS91n06Xw7SwWcMKik_8E0iHA@mail.gmail.com>
On Wed, 13 Apr 2011 14:10:46 -0700 Rory Jaffe <rsjaffe@gmail.com> wrote:
> I have a RAID5 array with 4 active devices and two spares. The spares
> are normally in sleep mode. I ran a resync with:
>
> echo repair > /sys/devices/virtual/block/md0/md/sync_action
>
> About 20 times (evenly spaced apart) during the resync, the spares
> were written to, waking them up. Is that behavior desired? It seems to
> me that it's a waste--I don't know why the resync would bother with
> the spares.
Yes, there is room for optimisation there. It really shouldn't write to
those devices. I guess I should try (again) to fix that.
Thanks for the report.
NeilBrown
prev parent reply other threads:[~2011-04-18 0:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 21:10 Resync intermittently writes to spare drives, waking them up Rory Jaffe
2011-04-14 8:32 ` David Brown
2011-04-18 0:55 ` NeilBrown [this message]
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=20110418105518.2ef04e47@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=rsjaffe@gmail.com \
/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).