From: NeilBrown <neilb@suse.de>
To: Wilson Jonathan <piercing_male@hotmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm, spin down never happens, do spare work the same?
Date: Sat, 21 Dec 2013 11:10:01 +1100 [thread overview]
Message-ID: <20131221111001.1fed992a@notabene.brown> (raw)
In-Reply-To: <BLU0-SMTP164EF98C4A2354CB5CE42AD98C40@phx.gbl>
[-- Attachment #1: Type: text/plain, Size: 2295 bytes --]
On Fri, 20 Dec 2013 23:56:14 +0000 Wilson Jonathan
<piercing_male@hotmail.com> wrote:
> I've noticed that with an active mdadm raid that there seems to be a
> periodic polling of the devices in the array which prevents the drives
> ever going into various slumber modes... and it also doesnt seem to make
> a difference if the file system on the array is mounted or not (slightly
> subjective as its more an observation than an in-depth testing).
>
> I'm guessing its to make sure the array is "ok" and is also used to
> update things such as /proc/mdstat and maybe other things related, so
> every now and then it goes "hi, are you there disks, whats your current
> state" for want of a better idea of the process.
>
> What I'm wondering is how mdadm treats the "spare" drives, does it also
> poll them periodically to the same time constraints as the active drives
> or does it just check at re-boot and maybe some other periodic time
> scales...
>
> The reason for enquiring is if a "spare" drive is kept alive to the same
> extent as a "live/active" drive then it means that a spare could have
> been powered up and accessed for the exact same time as a running
> "active" set of drives... which means that even though its never been
> used it could have had the same amount of time "live/spinning" as the
> existing arrays drives which would mean it is just as likely to fail due
> to [running] age as any other drive within the array, if however its
> only polled very sporadically (boot, maybe once a month, some other
> amount) then its "active life" is drastically shortened, which would
> mean its (to some degree) less likely to fail when its updated as a
> "live disk" when another member has failed... obviously baring spin up
> counts and other "power up=old=pre-fail" issues.
>
> Thanks in advance.
>
> Jon
>
>
Nope. md doesn't 'poll' devices at all.
if you ask to read from the array, it reads from devices.
If you ask to write to the array, it writes to devices (and maybe reads)
if you ask it to 'check' the array, it does.
IF it notices a spare and a missing device, it performs recovery.
If there is nothing to do, it does nothing.
What evidence do you have which led you to suspect some polling activity.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2013-12-21 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 23:56 mdadm, spin down never happens, do spare work the same? Wilson Jonathan
2013-12-21 0:10 ` 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=20131221111001.1fed992a@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=piercing_male@hotmail.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).