From: NeilBrown <neilb@suse.de>
To: Vincent Pelletier <plr.vincent@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Spin down
Date: Mon, 5 Dec 2011 17:11:15 +1100 [thread overview]
Message-ID: <20111205171115.044b1705@notabene.brown> (raw)
In-Reply-To: <CAF78GY0YdJ0c0WWpyDnnzitAec_7VZZnEsP_n_UHuec5JmVAng@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2778 bytes --]
On Sat, 3 Dec 2011 12:23:37 +0100 Vincent Pelletier <plr.vincent@gmail.com>
wrote:
> Hi.
>
> Short system description:
> up-to-date Debian sid, used on a NAS-ish machine (iscsi with
> open-iscsi's kernel module, nfs, dnsmask for netboot), ext4 FS over
> RAID1 on both system partition and exported data partitions.
>
> I would like disks containing raid arrays to spin down, but there are
> periodic disk writes which prevent this.
> They do not show up in iotop (although it does show a write activity
> in the topmost line).
> Enabling /proc/sys/vm/block_dump generates the following output:
>
> <7>[ 918.078079] md0_raid1(304): WRITE block 8 on sda1 (2 sectors)
> <7>[ 918.078169] md0_raid1(304): WRITE block 8 on sdc1 (2 sectors)
> <7>[ 918.092124] md1_raid1(311): WRITE block 8 on sda5 (2 sectors)
> <7>[ 918.092184] md1_raid1(311): WRITE block 8 on sdc5 (2 sectors)
> <7>[ 918.292627] md0_raid1(304): WRITE block 8 on sda1 (2 sectors)
> <7>[ 918.292714] md0_raid1(304): WRITE block 8 on sdc1 (2 sectors)
> <7>[ 918.308500] md1_raid1(311): WRITE block 8 on sda5 (2 sectors)
> <7>[ 918.308588] md1_raid1(311): WRITE block 8 on sdc5 (2 sectors)
> <7>[ 923.113309] md0_raid1(304): WRITE block 8 on sda1 (2 sectors)
> <7>[ 923.113397] md0_raid1(304): WRITE block 8 on sdc1 (2 sectors)
> <7>[ 923.129330] md1_raid1(311): WRITE block 8 on sda5 (2 sectors)
> <7>[ 923.129388] md1_raid1(311): WRITE block 8 on sdc5 (2 sectors)
> <7>[ 923.332489] md0_raid1(304): WRITE block 8 on sda1 (2 sectors)
> <7>[ 923.332545] md0_raid1(304): WRITE block 8 on sdc1 (2 sectors)
> <7>[ 923.348507] md1_raid1(311): WRITE block 8 on sda5 (2 sectors)
> <7>[ 923.348595] md1_raid1(311): WRITE block 8 on sdc5 (2 sectors)
>
> Note the 5-seconds pause between each half of this output.
> Block 8 seems to be the md superblock (dixit hexdump + description of
> md superblock), and "mdadm --examine" shows the "Update time" is being
> increased.
> Those arrays are in clean state, no synchronisation is happening and
> no checking that I know of (I would expect a lot of disk activity).
>
> Is there any reason why those writes are happening ?
> I can imagine a mechanism like filesystem superblock periodic
> flushing, but AFAIK it only happens when changes are happening (even
> if they are not flushed themselves), and I would expect the same to
> happen here.
> Is there any knob to control those writes ?
>
> Regards,
5 seconds suggests a bitmap update. Do you have an internal bitmap?
Try to remove it
mdadm --grow /dev/md0 --bitmap=none
and see if they stop.
Then try adding it back with a longer delay
mdadm --grow /dev/md0 --bitmap=internal --delay=60
What kernel version are you running?
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2011-12-05 6:11 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 [this message]
2011-12-05 7:49 ` Vincent Pelletier
2011-12-06 4:39 ` NeilBrown
2011-12-06 8:21 ` Vincent Pelletier
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=20111205171115.044b1705@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=plr.vincent@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.