From: Matt C <wago@phlinux.com>
To: David Brown <dave@codewhore.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: CCISS driver and disk failure...
Date: Wed, 5 Feb 2003 18:09:13 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.44.0302051806010.3082-100000@fubar.phlinux.com> (raw)
In-Reply-To: <20030204215358.GA6266@codewhore.org>
Hi David-
The only way we're able to do this on proliants is to use the *hack*
closed-source HP kernel modules cpqasm and cpqevt. We then run their 30+
userspace daemons that monitor the system via these 2 kernel modules. Slap
their hacked up ucd-snmpd on top of that and you get disk status
monitoring via SNMP on the machine.
On a redhat machine, that's the following RPMs from HP:
cmafdtn
cmanic
cmastor
cmasvr
cpqhealth
ucd-snmp (from HP, of course)
It's a nasty mess, though, so if the cciss author had the time to put disk
fail logging into the driver, that'd be amazingly cool.
-Matt
On Tue, 4 Feb 2003, David Brown wrote:
> Hi:
>
> Does anyone know of an easy way to get messages (via syslog or
> otherwise) when a member disk of a CCISS SMART-2 raid array fails?
> Grepping through drivers/block/cciss.c didn't yield any obvious
> printk's. My gut feeling is that one could get the disk failure
> information through one of the CCISS_PASSTHRU ioctls(); I saw some
> reference to a similar call in code for monitoring the cpqarray
> driver.
>
> HP appears to have some sort of management suite, but it appears to
> require X11 server-side, which isn't an option on this machine.
>
> Is there an easy way to get disk failure information from the CCISS
> driver, or should I continue relying on the pretty LEDs? :)
>
>
> Thanks in advance,
>
> - Dave
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-02-06 1:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 21:53 David Brown
2003-02-06 2:09 ` Matt C [this message]
2003-02-06 23:15 ` Matt C
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=Pine.LNX.4.44.0302051806010.3082-100000@fubar.phlinux.com \
--to=wago@phlinux.com \
--cc=dave@codewhore.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®