linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Robert Woodworth <robertjwoodworth@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: SES Enclosure Management.
Date: Wed, 15 Feb 2012 07:31:30 +1100	[thread overview]
Message-ID: <20120215073130.792d4fae@notabene.brown> (raw)
In-Reply-To: <CAB9NSeUBZXdGRkNNzYjC-KmJjv_AUp4bD_dJH2XyzkuO7PUPcw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2451 bytes --]

On Tue, 14 Feb 2012 10:30:37 -0700 Robert Woodworth
<robertjwoodworth@gmail.com> wrote:

> Has anyone ever thought of integrating SES managed enclosures into the
> kernel RAID system?  I briefly looked through the archives and have
> not found anything on the topic.
> 
> Some HW based RAID controllers do this flawlessly now, there is no
> reason why the kernel RAID cannot also.  (LSI MegaRAID)
> 
> 1) When a drive is part if a managed enclosure, the RAID system should
> address it by location instead of by enumerated device node.  The SES
> device in the enclosure can map the physical slot to a physical drive.
>  The RAID admin (mdamd) should be able to add/fail/identify devices
> based on slot.

Does this just mean that the admin should using names in /dev/disk/by-path/
rather than /dev/sdXX to address devices?  What can md or mdadm do to help?

> 
> 2) If the RAID system fails a drive, it should notify the SES
> management and turn on the fail bit and the fail LED.

"mdadm --monitor" will run a script on drive failure.  This could easily
notify the SES management.

So maybe all we need here is a script to plug in to mdadm... Would you like
to write one?

> 
> 3) The RAID system should be able to turn on the 'identify' bit and
> LEDs for an array or a single drive.

Again, it sounds like you just need a script to ask mdadm which devices are
included in a given array, and then do whatever magic is needed to turn on
the light.
It is fairly easy to extra the device list from the output of
  mdadm --detail --brief --verbose /dev/md/whatever

but it might be good to make it easier to extra from
  mdadm --detail --export /dev/md/whatever

Would you like to write such a script?

> 
> I'm currently doing firmware on a managed enclosure.  Although my
> vendor only supports LSI MegaRAID, there is no reason why my
> enclosures cannot work in the same manner on a kernel RAID system.
> 
> 
> 
> Request for comments...

It sounds to me like you just need a few scripts to provide some
enclosure-specific functionality.  I would be happy to include them in the
mdadm distribution.

Or maybe there is something that I didn't understand??

Thanks,
NeilBrown



> --
> 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


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-02-14 20:31 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 [this message]
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
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=20120215073130.792d4fae@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=robertjwoodworth@gmail.com \
    /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).