From: NeilBrown <neilb@suse.de>
To: Jan Ceuleers <jan.ceuleers@computer.org>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: dmesg deluge: RAID1 conf printout
Date: Sun, 22 Apr 2012 07:00:41 +1000 [thread overview]
Message-ID: <20120422070041.7e4b95e7@notabene.brown> (raw)
In-Reply-To: <4F92BC43.3010603@computer.org>
[-- Attachment #1: Type: text/plain, Size: 2640 bytes --]
On Sat, 21 Apr 2012 15:55:15 +0200 Jan Ceuleers <jan.ceuleers@computer.org>
wrote:
> Hi
>
> Ever since I installed a 3.2 kernel on my Ubuntu 11.04 system, dmesg
> began being flooed with messages such as the following:
>
> [15746.465106] disk 1, wo:0, o:1, dev:sdb2
> [15748.100302] RAID1 conf printout:
> [15748.100306] --- wd:2 rd:2
> [15748.100310] disk 0, wo:0, o:1, dev:sdd2
> [15748.100313] disk 1, wo:0, o:1, dev:sdb2
> [15748.438638] RAID1 conf printout:
> [15748.438642] --- wd:2 rd:2
> [15748.438646] disk 0, wo:0, o:1, dev:sdd2
> [15748.438649] disk 1, wo:0, o:1, dev:sdb2
> [15751.181020] RAID1 conf printout:
> [15751.181026] --- wd:2 rd:2
> [15751.181030] disk 0, wo:0, o:1, dev:sdd2
> [15751.181034] disk 1, wo:0, o:1, dev:sdb2
> [15751.630244] RAID1 conf printout:
> [15751.630250] --- wd:2 rd:2
> [15751.630255] disk 0, wo:0, o:1, dev:sdd2
> [15751.630259] disk 1, wo:0, o:1, dev:sdb2
> [15754.004658] RAID1 conf printout:
> [15754.004662] --- wd:2 rd:2
> [15754.004666] disk 0, wo:0, o:1, dev:sdd2
> [15754.004670] disk 1, wo:0, o:1, dev:sdb2
> [15754.312749] RAID1 conf printout:
> [15754.312754] --- wd:2 rd:2
> [15754.312758] disk 0, wo:0, o:1, dev:sdd2
> [15754.312762] disk 1, wo:0, o:1, dev:sdb2
> [15759.231107] RAID1 conf printout:
> [15759.231112] --- wd:2 rd:2
> [15759.231115] disk 0, wo:0, o:1, dev:sdd2
> [15759.231118] disk 1, wo:0, o:1, dev:sdb2
>
> (etc, ad infinitum)
>
> I'm now running a 3.3 kernel and it's still happening. My RAID sets are
> working just fine; it's just this nuisance log spamming that's annoying.
>
> Anything I can do about that?
Best thing you can do it report it and hope some maintainer notices and helps
out. Oh wait, you did that :-)
Looks like:
commit 7bfec5f35c68121e7b1849f3f4166dd96c8da5b3
is at fault. It causes md to attempt to add spares into the array more often.
Would I be right in guessing that you have one spare in this array?
If you remove the spare, the messages should stop.
I think I know how I'll fix it but it'll have to wait for tomorrow. Then
I'll send you a patch to test.
Thanks for the report,
NeilBrown
>
> root@zotac:~# uname -a
> Linux zotac 3.3.2-030302-generic #201204131335 SMP Fri Apr 13 17:36:17
> UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> root@zotac:~# mdadm -V
> mdadm - v3.1.4 - 31st August 2010
>
>
> Thanks, Jan
> --
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-04-21 21:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 13:55 dmesg deluge: RAID1 conf printout Jan Ceuleers
2012-04-21 21:00 ` NeilBrown [this message]
2012-04-22 8:17 ` Jan Ceuleers
2012-04-22 17:21 ` Jan Ceuleers
2012-04-22 23:48 ` NeilBrown
2012-04-23 7:01 ` Jan Ceuleers
2012-04-27 1:30 ` NeilBrown
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=20120422070041.7e4b95e7@notabene.brown \
--to=neilb@suse.de \
--cc=jan.ceuleers@computer.org \
--cc=linux-raid@vger.kernel.org \
/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.