From: Bill Davidsen <davidsen@tmr.com>
To: Carlos Carvalho <carlos@fisica.ufpr.br>
Cc: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: idle array consuming cpu ??!!
Date: Tue, 22 Jan 2008 17:53:29 -0500 [thread overview]
Message-ID: <479673E9.8030301@tmr.com> (raw)
In-Reply-To: <18325.21501.507878.267465@fisica.ufpr.br>
Carlos Carvalho wrote:
> Neil Brown (neilb@suse.de) wrote on 21 January 2008 12:15:
> >On Sunday January 20, carlos@fisica.ufpr.br wrote:
> >> A raid6 array with a spare and bitmap is idle: not mounted and with no
> >> IO to it or any of its disks (obviously), as shown by iostat. However
> >> it's consuming cpu: since reboot it used about 11min in 24h, which is quite
> >> a lot even for a busy array (the cpus are fast). The array was cleanly
> >> shutdown so there's been no reconstruction/check or anything else.
> >>
> >> How can this be? Kernel is 2.6.22.16 with the two patches for the
> >> deadlock ("[PATCH 004 of 4] md: Fix an occasional deadlock in raid5 -
> >> FIX") and the previous one.
> >
> >Maybe the bitmap code is waking up regularly to do nothing.
> >
> >Would you be happy to experiment? Remove the bitmap with
> > mdadm --grow /dev/mdX --bitmap=none
> >
> >and see how that affects cpu usage?
>
> Confirmed, removing the bitmap stopped cpu consumption.
Looks like quite a bit of CPU going into idle arrays here, too.
--
Bill Davidsen <davidsen@tmr.com>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
next prev parent reply other threads:[~2008-01-22 22:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 23:00 idle array consuming cpu ??!! Carlos Carvalho
2008-01-21 1:15 ` Neil Brown
2008-01-21 1:33 ` Carlos Carvalho
2008-01-22 2:25 ` Carlos Carvalho
2008-01-22 22:53 ` Bill Davidsen [this message]
2008-01-22 23:34 ` Carlos Carvalho
2008-01-24 2:16 ` Bill Davidsen
2008-01-24 4:55 ` Neil Brown
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=479673E9.8030301@tmr.com \
--to=davidsen@tmr.com \
--cc=carlos@fisica.ufpr.br \
--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).