From: Fabien Salvi <fabien@cri74.org>
To: linux-scsi@vger.kernel.org
Subject: (RAID controller) Unified way to get alarms
Date: Tue, 02 Mar 2004 10:05:38 +0100 [thread overview]
Message-ID: <40444E62.2070705@cri74.org> (raw)
Hello,
I've noticed each PCI Raid card (for example ICP-Vortex ,LSILogic or
ServerRAID) with their own driver uses a specific way to get alarms.
We could have several types of alarm or warning, depending on the event
(degraded RAID, bad sectors detected, temperature sensor, etc...) :
- audible alarm ==> the more classical signal
- messages in kernel logs ==> not all drivers support this and each one
send different messages
- messages in console ==> idem
- informations in /proc/scsi/... (for 2.4 kernel) ==> for example in
/proc/scsi/gdth/0 with ICP controllers
- others ?
Unlike proprietary OS with proprietary (manufacter) driver, we have the
ability under linux and with opensource drivers to use an unified way to
get warning and alarms from a RAID controller.
Why don't use it ?
It will permit a single tool to manage these events without writing one
per driver...
--
Fabien SALVI
next reply other threads:[~2004-03-02 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 9:05 Fabien Salvi [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-02 14:37 (RAID controller) Unified way to get alarms Salyzyn, Mark
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=40444E62.2070705@cri74.org \
--to=fabien@cri74.org \
--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