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 08:16:11 +1100 [thread overview]
Message-ID: <20120215081611.3cc31578@notabene.brown> (raw)
In-Reply-To: <4F3AC828.5000202@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1960 bytes --]
On Tue, 14 Feb 2012 13:46:32 -0700 Robert Woodworth
<robertjwoodworth@gmail.com> wrote:
> On 02/14/2012 01:31 PM, NeilBrown wrote:
> > 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?
> I don't like the /by-path/ too well, it is not human readable. I would
> propose that the SES module that is already in the base kernel be
> expanded to provide a /dev/disk/by-location/<enclosureID>/<slot> ->
> /dev/sdXY
It isn't the kernel that provides these links, it is udev.
If there is some tool that can extract the enclosureID and slot values, then
one or 2 lines in a udev 'rules' file should be able to create the links.
> >
> The one piece that could be included in the kernel level is the display
> of /proc/mdstat to show the enclosureID and slot number
I'm finding /proc/mdstat increasingly distasteful. It is very convenient but
hard to extend usefully.
I' rather create something like
mdadm --status
which reported the status of all (or some) arrays with similar usability to
/proc/mdstat, but more room to extend it.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-02-14 21:16 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
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 [this message]
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=20120215081611.3cc31578@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).