From: Joe Landman <joe.landman@gmail.com>
To: Jeff Johnson <jeff.johnson@aeoncomputing.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: SES Enclosure Management.
Date: Wed, 15 Feb 2012 09:54:15 -0500 [thread overview]
Message-ID: <4F3BC717.7060609@gmail.com> (raw)
In-Reply-To: <4F3AD0F0.7010306@aeoncomputing.com>
On 02/14/2012 04:24 PM, Jeff Johnson wrote:
>> 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.
The tools we've been working on have been trying to correlate this by
various methods though these vary by HBA and other issues. UDEV rules
can often produce some interesting results (and not in a good way, and
not just for disks).
--
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics Inc.
email: landman@scalableinformatics.com
web : http://scalableinformatics.com
http://scalableinformatics.com/sicluster
phone: +1 734 786 8423 x121
fax : +1 866 888 3112
cell : +1 734 612 4615
next prev parent reply other threads:[~2012-02-15 14:54 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 [this message]
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=4F3BC717.7060609@gmail.com \
--to=joe.landman@gmail.com \
--cc=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).