From: Bill Davidsen <davidsen@tmr.com>
To: Neil Brown <neilb@suse.de>
Cc: fibre raid <fibreraid@gmail.com>,
Christopher Chen <muffaleta@gmail.com>,
SandeepKsinha <sandeepksinha@gmail.com>,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: "raid array not clean" messages
Date: Thu, 21 May 2009 14:38:02 -0400 [thread overview]
Message-ID: <4A159F8A.5070302@tmr.com> (raw)
In-Reply-To: <18964.62098.885221.299555@notabene.brown>
Neil Brown wrote:
> On Thursday May 21, fibreraid@gmail.com wrote:
>
>> I have no problem with this message being written to
>> /var/log/messages, but in our case, we don't want it on the console.
>> We want the console to only be there for kernel crash dumps (if they
>> occur), nothing else.
>>
>
> I feel you are a bit optimistic...
>
> But I guess what you are really asking is for the message to be
> printed with a lower priority than KERN_ERR - maybe KERN_INFO.
> It is in drivers/md/md.c at the end of analyze_sbs.
>
> You would need to compile a new kernel to achieve that.
>
Since it is actually informational rather than an error, I would think
KERN_INFO would be more correct for all users. Then people who want
stuff like that can play with their syslog configuration to see it if
they want. I agree that conditions which do not require intervention to
correct them are not errors, messages about them are for informational
purposes. Hardware errors and failure in unexpected places don't need to
bother the operator (for whatever definition of operator you like).
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
"You are disgraced professional losers. And by the way, give us our money back."
- Representative Earl Pomeroy, Democrat of North Dakota
on the A.I.G. executives who were paid bonuses after a federal bailout.
prev parent reply other threads:[~2009-05-21 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 4:36 "raid array not clean" messages fibre raid
2009-05-21 4:49 ` SandeepKsinha
2009-05-21 4:55 ` fibre raid
2009-05-21 4:56 ` Christopher Chen
2009-05-21 5:11 ` fibre raid
2009-05-21 6:20 ` Neil Brown
2009-05-21 18:38 ` Bill Davidsen [this message]
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=4A159F8A.5070302@tmr.com \
--to=davidsen@tmr.com \
--cc=fibreraid@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=muffaleta@gmail.com \
--cc=neilb@suse.de \
--cc=sandeepksinha@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 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).