From: NeilBrown <neilb@suse.com>
To: Theophanis Kontogiannis <tkonto@gmail.com>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Question on blocks periodic writes
Date: Thu, 10 Nov 2016 13:00:05 +1100 [thread overview]
Message-ID: <8760nwm6vu.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <CAOzB0-6NYUqrzUyx3iQ8CbPwFh-dctKTVwE6GKupdYM-8AfOrg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2261 bytes --]
On Thu, Nov 10 2016, Theophanis Kontogiannis wrote:
> Hello All,
>
> I am in the middle of bringing my server's power consumption to an
> absolute minimum.
>
> Have already reduced idle power from 110W to 52W (including 10W
> consumed by the UPS).
>
> Having enabled spin down to all 5 x 2TB disks, with 5 seconds idle
> times, I noticed that the disks wake up quite often without the server
> doing anything actual.
>
> Following
>
> 'echo 1 > /proc/sys/vm/block_dump'
>
> I can not miss that
>
> 'dmesg -c'
>
> reports frequent messages like:
>
> [ 8662.496150] md0_raid6(631): WRITE block 16 on sda3 (8 sectors)
> [ 8662.496185] md0_raid6(631): WRITE block 16 on sdf3 (8 sectors)
> [ 8662.496253] md0_raid6(631): WRITE block 16 on sdg3 (8 sectors)
> [ 8662.496269] md0_raid6(631): WRITE block 16 on sdd3 (8 sectors)
> [ 8662.496282] md0_raid6(631): WRITE block 16 on sde3 (8 sectors)
These are probably the md bitmap being updated.
If you provided some basic detail about you array like
mdadm --detail /dev/md1
mdadm --examine /dev/sda3
it would be easier to be sure.
> [ 8664.849252] md0_raid6(631): WRITE block 8 on sda3 (1 sectors)
> [ 8664.849276] md0_raid6(631): WRITE block 8 on sdf3 (1 sectors)
> [ 8664.849287] md0_raid6(631): WRITE block 8 on sdg3 (1 sectors)
> [ 8664.849298] md0_raid6(631): WRITE block 8 on sdd3 (1 sectors)
> [ 8664.849352] md0_raid6(631): WRITE block 8 on sde3 (1 sectors)
This is probably the superblock being updated.
> [ 8664.858104] xfsaild/md1(658): WRITE block 0 on md1 (8 sectors)
This is XFS doing something. md cannot possibly stop all IO while the
filesystem performs occasional IO. If these continue, you need to
discuss with xfs developers how to stop it. If the writes to individual
drives continue after there are no writes to 'md1', then it is worth
coming back here to ask.
> [ 8664.902688] md0_raid6(631): WRITE block 16 on sda3 (8 sectors)
> [ 8665.177050] md0_raid6(631): WRITE block 16 on sda3 (8 sectors)
> [ 8670.269138] md0_raid6(631): WRITE block 16 on sda3 (8 sectors)
> [ 8680.269050] md0_raid6(631): WRITE block 16 on sda3 (8 sectors)
The delay here is 270ms, then 5 seconds, then 10 seconds.
Does it reach a stable state? What is the period in the stable state?
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
next prev parent reply other threads:[~2016-11-10 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 17:20 Question on blocks periodic writes Theophanis Kontogiannis
2016-11-10 2:00 ` NeilBrown [this message]
2016-11-10 16:10 ` Wols Lists
2016-11-11 1:52 ` NeilBrown
2016-11-11 12:11 ` Theophanis Kontogiannis
2016-11-11 12:13 ` Theophanis Kontogiannis
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=8760nwm6vu.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=linux-raid@vger.kernel.org \
--cc=tkonto@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).