From: Jan Ceuleers <jan.ceuleers@computer.org>
To: NeilBrown <neilb@suse.de>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: dmesg deluge: RAID1 conf printout
Date: Mon, 23 Apr 2012 09:01:45 +0200 [thread overview]
Message-ID: <4F94FE59.20307@computer.org> (raw)
In-Reply-To: <20120423094853.15683cd6@notabene.brown>
NeilBrown wrote:
> The following should fix it.
Neil,
Since I had not been running a self-compiled kernel when I reported
this, I first reproduced the issue on vanilla 3.3.0: git clone, git
checkout, build (using the Ubuntu config file for 3.3.0), install, boot.
The spares were not being added to either RAID 1 set, and the logs were
not being flooded. The behaviour however began immediately when I added
the spares manually.
I then built a kernel with your patch on top, and upon booting the
spares were being added automatically, and the logs are not being
spammed. The problem therefore indeed appears to be solved.
Tested-by: Jan Ceuleers <jan.ceuleers@computer.org>
Thanks, Jan
next prev parent reply other threads:[~2012-04-23 7:01 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
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 [this message]
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=4F94FE59.20307@computer.org \
--to=jan.ceuleers@computer.org \
--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).