From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Moore, Eric" <Eric.Moore@lsil.com>
Cc: linux-scsi@vger.kernel.org
Subject: RE: [PATCH 5/8] fusion - adding verbose messages for RAID actions
Date: Mon, 30 Jan 2006 15:17:51 -0600 [thread overview]
Message-ID: <1138655871.3283.34.camel@mulgrave> (raw)
In-Reply-To: <F331B95B72AFFB4B87467BE1C8E9CF5F22118D@NAMAIL2.ad.lsil.com>
On Mon, 2006-01-30 at 12:28 -0700, Moore, Eric wrote:
> I didn't know that occurred on boot. I thought those messages only came
> when
> raid status change occured, such as a drive failing or volume coming
> online after resycn completed.
It's quiescing the RAID prior to performing Domain validation
(apparently we get three messages per quiesce: one for the array and one
each for the two halves of the mirror).
> What is your recommendation for this?
Perhaps use the KERN_ logging system to work for us: so most array
event messages would be KERN_DEBUG that won't ordinarily display for the
less critical messages.
James
next prev parent reply other threads:[~2006-01-30 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 19:28 [PATCH 5/8] fusion - adding verbose messages for RAID actions Moore, Eric
2006-01-30 21:17 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-17 1:53 Moore, Eric
2006-01-17 13:43 ` Christoph Hellwig
2006-01-30 19:22 ` James Bottomley
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=1138655871.3283.34.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Eric.Moore@lsil.com \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox