have a look at this thread:-
http://mail.opensolaris.org/pipermail/zfs-discuss/2009-September/032349.html
we discussed this a while back.
SHOUJIN WANG wrote:
Hi there,
What I am tring to do is: Build a NAS storage server based on the following hardware architecture:
Server-->SAS HBA--->SAS JBOD
I plugin 2 SAS HBA cards into a X86 box, I also have 2 SAS I/O Modules on SAS JBOD. From each HBA card, I have one SAS cable which connects to SAS JBOD.
Configured MPT successfully on server, I can see the single multipahted disks likes the following:
r...@super01:~# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t5000C5000D34BEDFd0 <SEAGATE-ST31000640SS-0001-931.51GB>
/scsi_vhci/d...@g5000c5000d34bedf
1. c0t5000C5000D34BF37d0 <SEAGATE-ST31000640SS-0001-931.51GB>
/scsi_vhci/d...@g5000c5000d34bf37
2. c0t5000C5000D34C727d0 <SEAGATE-ST31000640SS-0001-931.51GB>
/scsi_vhci/d...@g5000c5000d34c727
3. c0t5000C5000D34D0C7d0 <SEAGATE-ST31000640SS-0001-931.51GB>
/scsi_vhci/d...@g5000c5000d34d0c7
4. c0t5000C5000D34D85Bd0 <SEAGATE-ST31000640SS-0001-931.51GB>
/scsi_vhci/d...@g5000c5000d34d85b
The problem is: if one of disks failed, I don't know how to locate the disk in chasiss. It is diffcult for failed disk replacement.
Is there any utility in opensoalris which can be used to locate/blink the failed disk(or do we have any michanism to implement the SES command in bond of SAS)? Or do we have a tool to map the multipathing device ID to the original single pathing device ID likes the following?
c0t5000C5000D34BF37d0
|----c2t0d0
\----c3t0d0
Regards,
Autumn Wang.
www.eagle.co.nz
This email is confidential and may be legally
privileged. If received in error please destroy and immediately notify
us.
|
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
