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 13:22:12 -0600 [thread overview]
Message-ID: <1138648932.3283.28.camel@mulgrave> (raw)
In-Reply-To: <F331B95B72AFFB4B87467BE1C8E9CF5F1AAC81@NAMAIL2.ad.lsil.com>
On Mon, 2006-01-16 at 18:53 -0700, Moore, Eric wrote:
> A customer request to send raid asyn actions
> from firmware to the event syslog. This shows
> when raid volumes go degraded, or complete resync,
> or volumes created/deleted, etc.
I've put this in, but it really is quite verbose. This is what my
single IM RAID gives on boot:
mptbase: ioc1: RAID STATUS CHANGE for VolumeID 0
mptbase: ioc1: volume is now optimal, enabled, quiesced
mptbase: ioc1: RAID STATUS CHANGE for PhysDisk 0
mptbase: ioc1: PhysDisk is now online, quiesced
mptbase: ioc1: RAID STATUS CHANGE for PhysDisk 1
mptbase: ioc1: PhysDisk is now online, quiesced
mptbase: ioc1: RAID STATUS CHANGE for VolumeID 0
mptbase: ioc1: volume is now optimal, enabled
mptbase: ioc1: RAID STATUS CHANGE for PhysDisk 0
mptbase: ioc1: PhysDisk is now online
mptbase: ioc1: RAID STATUS CHANGE for PhysDisk 1
mptbase: ioc1: PhysDisk is now online
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
mptbase: ioc1: RAID STATUS CHANGE for VolumeID 0
mptbase: ioc1: volume is now optimal, enabled, quiesced
mptbase: ioc1: RAID STATUS CHANGE for PhysDisk 0
mptbase: ioc1: PhysDisk is now online, quiesced
mptbase: ioc1: RAID STATUS CHANGE for PhysDisk 1
mptbase: ioc1: PhysDisk is now online, quiesced
mptbase: ioc1: RAID STATUS CHANGE for VolumeID 0
mptbase: ioc1: volume is now optimal, enabled
mptbase: ioc1: RAID STATUS CHANGE for PhysDisk 0
mptbase: ioc1: PhysDisk is now online
mptbase: ioc1: RAID STATUS CHANGE for PhysDisk 1
mptbase: ioc1: PhysDisk is now online
Which is rather a lot of spew for a single device ...
James
next prev parent reply other threads:[~2006-01-30 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 1:53 [PATCH 5/8] fusion - adding verbose messages for RAID actions Moore, Eric
2006-01-17 13:43 ` Christoph Hellwig
2006-01-30 19:22 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-30 19:28 Moore, Eric
2006-01-30 21:17 ` 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=1138648932.3283.28.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 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.