From: Vincent Pelletier <plr.vincent@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org, kobras@linux.de
Subject: Re: Spin down
Date: Tue, 6 Dec 2011 09:21:44 +0100 [thread overview]
Message-ID: <201112060921.45058.plr.vincent@gmail.com> (raw)
In-Reply-To: <20111206153923.203df175@notabene.brown>
Le mardi 06 décembre 2011 05:39:23, NeilBrown a écrit :
> Hmm... I cannot reproduce this which makes it harder.
Rebooting on a CONFIG_DYNAMIC_DEBUG-enabled kernel and ssh'ing soon enough, I
think I found the culprit: noflushd process.
(cc'ing its author)
<noflushd intro>
noflushd is a nice daemon helping suspending disks by tracking disk *read*
activity. When enough time has passed without reads, it disables automated
flushing (echo 0 > /proc/sys/vm/dirty_writeback_centisecs) and takes over
flushing for individual block devices (only flushing spinning devices).
This way, there is no extra delay in writes when disk spins, and only an
explicit flush (or read) will cause disk to spin up.
</noflushd intro>
I enabled block_trace to see if the problem was still here, and there was no
activity for 10+ seconds. Then I saw traces for noflushd process, and
previously-reported writes started ticking every 5s. 5s is the default (at
least, on my machine) writeback period, so it's what noflushd uses when taking
over per-device flushing.
I stopped noflushd process, and tada, problem solved.
FWIW, noflushd does individual flushes by opening bock device for write, and
fsync()'ing it.
Sorry for the noise.
Regards,
--
Vincent Pelletier
--
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
prev parent reply other threads:[~2011-12-06 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 11:23 Spin down Vincent Pelletier
2011-12-05 6:11 ` NeilBrown
2011-12-05 7:49 ` Vincent Pelletier
2011-12-06 4:39 ` NeilBrown
2011-12-06 8:21 ` Vincent Pelletier [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=201112060921.45058.plr.vincent@gmail.com \
--to=plr.vincent@gmail.com \
--cc=kobras@linux.de \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).