linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Johnson <jeff.johnson@aeoncomputing.com>
To: linux-raid@vger.kernel.org
Subject: Re: SES Enclosure Management.
Date: Tue, 14 Feb 2012 13:24:00 -0800	[thread overview]
Message-ID: <4F3AD0F0.7010306@aeoncomputing.com> (raw)
In-Reply-To: <4F3ACDD7.5040506@gmail.com>

On 2/14/12 1:10 PM, Robert Woodworth wrote:
> On 02/14/2012 02:06 PM, Jeff Johnson wrote:
>> On 2/14/12 12:58 PM, Joe Landman wrote:
>>> <..snip...>
>>>> enclosure provides a device on the SCSI bus and you exclusively
>>>> communicate with that device regardless of the HBA. Most HW RAIDs (LSI
>>>> MegaRAID) will hide the SES device exactly like they hide the physical
>>>> disks.
>>>>
>>> A true managed enclosure has nothing to do with the HBA. A managed
>>>
>>> Ok.  Let me look to see if we can do this.  If so, we should be able 
>>> to help contribute some scripts.
>> I've been doing this for a while. In SES the various elements (slot, 
>> power supplies, fans, etc) are named.  At least if your JBOD vendor 
>> has their **** together. There is no need to decipher arrays of hex 
>> values and modify bits to assert control. Once you know the names of 
>> your elements you can address them by name for status and control 
>> (fault LED, power on/off, temps, etc).
>>
>> --Jeff
>
> Correct!  Now I just want to connect the RAID system to the SES system 
> so that when a disk fails, the kernel module that failed the disk can 
> light up the LED.
>
> I work for one of those vendors, it's my job to have our **** together.
>
The trick is to map the disk element names to the block device names. 
Different SAS HBAs and drivers can enumerate the devices differently. 
Persistence settings can muck things up as well. Sometimes a failed 
block device at /dev/sdf can appear as /dev/sdr when replaced. You could 
use udev rules to create alternate block device names but so far, for 
important data, I've seen no substitute for a pair of knowledgeable 
human eyes analyzing a failure and confirming a failed drive by 
corelating WWNs, etc.

--Jeff

-- 
------------------------------
Jeff Johnson
Manager
Aeon Computing

jeff.johnson@aeoncomputing.com
www.aeoncomputing.com
t: 858-412-3810 x101   f: 858-412-3845
m: 619-204-9061

4905 Morena Boulevard, Suite 1313 - San Diego, CA 92117


  reply	other threads:[~2012-02-14 21:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14 17:30 SES Enclosure Management Robert Woodworth
2012-02-14 20:31 ` NeilBrown
2012-02-14 20:42   ` Joe Landman
2012-02-14 20:53     ` Robert Woodworth
2012-02-14 20:58       ` Joe Landman
2012-02-14 21:06         ` Jeff Johnson
2012-02-14 21:10           ` Robert Woodworth
2012-02-14 21:24             ` Jeff Johnson [this message]
2012-02-15 14:54               ` Joe Landman
2012-02-16 19:00       ` Benjamin ESTRABAUD
2012-02-16 19:12         ` Robert Woodworth
2012-02-21 18:55           ` Benjamin ESTRABAUD
2012-02-14 20:46   ` Robert Woodworth
2012-02-14 21:16     ` NeilBrown
2012-02-14 20:38 ` Joe Landman

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=4F3AD0F0.7010306@aeoncomputing.com \
    --to=jeff.johnson@aeoncomputing.com \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).