All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Vincent Pelletier <plr.vincent@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Spin down
Date: Tue, 6 Dec 2011 15:39:23 +1100	[thread overview]
Message-ID: <20111206153923.203df175@notabene.brown> (raw)
In-Reply-To: <CAF78GY0u89KvZhEZQ64GxWeDpBCT6cdAJ+xaGm=z7O_2gKTYTA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1897 bytes --]

On Mon, 5 Dec 2011 08:49:03 +0100 Vincent Pelletier <plr.vincent@gmail.com>
wrote:

> On Mon, Dec 5, 2011 at 7:11 AM, NeilBrown <neilb@suse.de> wrote:
> > 5 seconds suggests a bitmap update.  Do you have an internal bitmap?
> 
> I don't, but I enabled it on those arrays before with default delay.
> I then removed it when I suspected (with help of block_dump) it to
> cause spin-ups, and I noticed an improvement. Recently, the machine
> was restarted (once on 3.0 kernel, and again to update to 3.1), and
> after both restarts those 5s periodic writes occurred.
> 
> > Then try adding it back with a longer delay
> >  mdadm --grow /dev/md0 --bitmap=internal --delay=60
> 
> Adding bitmaps on both arrays (md0 and md1), 5s periodic writes disappear.
> Removing bitmaps seems to preserve the improvement.
> 
> Could the delay setting have survived on-disk and be used when
> initializing the array, but cleared when mdadm later disables bitmap
> usage ?
> 
> > What kernel version are you running?
> 
> 3.1.4, according to dpkg:
> ii  linux-image-3.1.0-1-amd64                   3.1.4-1
>                      Linux 3.1 for 64-bit PCs
> 
> Regards,


Hmm... I cannot reproduce this which makes it harder.

Can you enable dynamic debugging on md?
Make sure CONFIG_DYNAMIC_DEBUG is set, mount debugfs on /sys/kernel/debug and

 echo module md_mod +p > /sys/kernel/debug/dynamic_debug/control

then look for extra messages in the kernel logs, starting "md:" most likely.

You'll almost certainly see something like

[ 1851.559629] md: waking up MD thread md0_raid1.
[ 1851.625819] md: updating md0 RAID superblock on device (in sync 1)
[ 1851.656878] md: (write) sdb's sb offset: 8
[ 1851.656915] md: (write) sda's sb offset: 8


every 5 seconds.  If you could confirm that and report if there is anything
else reported that might help.

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2011-12-06  4:39 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 [this message]
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=20111206153923.203df175@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.