linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Lethe <david@santools.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
	Linux RAID Mailing List <linux-raid@vger.kernel.org>
Cc: "J.H." <warthog9@kernel.org>
Subject: Re: Chassis manager?
Date: Wed, 15 Jul 2009 15:46:01 -0500	[thread overview]
Message-ID: <C683AA39.B563%david@santools.com> (raw)
In-Reply-To: <4A5E2D6F.3080000@zytor.com>

Assuming you enclosure is SES or SAF-TE compliant, then we've got a $90
package that does this.

Full environmental reporting (Fan speed, drive bays, temperature, voltage,
power supply, audible alarms, LEDs, etc ... as well as manipulation and
diagnostics.

But some gotchas --- in particular with drive failures. Only a catastriphic
failure will cause an enclosure to light a drive slot.  I.e, a head crash
won't necessarily result in a drive by let up. It is not the  job of an
enclosure to monitor drive health. SAS/FC/SCSI controller cards won't
necessarily do this either as, depending on the architecture, they send
the command to light up a drive to the disk, which is ignored by the
enclosure.

Our code will let you programmatically manipulate everything, but per the
spec, not every enclosure is obligated to support all that you wish to do.
No matter what, you'll need to set up a daemon that monitors whatever you
consider to be good enough reason to light up a drive bay, and there is no
"best" way that fits everything.

The SES spec also allows for lighting up a LED to indicate a drive needs to
be replaced in addition to a fault LED, but not all enclosures have this.
SAF-TE, used for SCSI-attached enclosures is quite dumb and likely won't let
you programmatically do anything but report basic info.

The manual is: http://www.santools.com/smart/unix/manual

Best to take this offline, feel free to contact me directly. It  is my
company, and I wrote most of the code
David  @ santools dot com


On 7/15/09 2:26 PM, "H. Peter Anvin" <hpa@zytor.com> wrote:

> Hi all,
> 
> Does anyone happen to know of a chassis manager for Linux softraid?
> What I mean with that is something that can provide the user interface
> that hardware RAID provides for a co-lo'd server: light up the error
> light on a dead disk, have a tech walk up and swap the drive (without
> administrator intervention; the tech does not have or need access to the
> system), and then automatically start the rebuild?
> 
> -hpa
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 



      reply	other threads:[~2009-07-15 20:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15 19:26 Chassis manager? H. Peter Anvin
2009-07-15 20:46 ` David Lethe [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=C683AA39.B563%david@santools.com \
    --to=david@santools.com \
    --cc=hpa@zytor.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=warthog9@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;
as well as URLs for NNTP newsgroup(s).