On 2/14/12 1:10 PM, Robert Woodworth wrote:
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.
On 02/14/2012 02:06 PM, Jeff Johnson wrote:
On 2/14/12 12:58 PM, Joe Landman wrote:
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).
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
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.
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.
t: 858-412-3810 x101 f: 858-412-3845
4905 Morena Boulevard, Suite 1313 - San Diego, CA 92117
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html