OpenSolaris
Discussions Communities Projects Download Source Browser

Home » OpenSolaris Forums » storage » discuss

Thread: Disk locating in OpenSolaris/Solaris 10

Welcome, Guest Help
Login Login
Guest Settings Guest Settings
Reply to this Thread Reply to this Thread Search Forum Search Forum Back to Thread List Back to Thread List

Permlink Replies: 6 - Last Post: Nov 3, 2009 3:07 PM by: James C. McPher...
autumnw

Posts: 11
From:

Registered: 6/30/08
Disk locating in OpenSolaris/Solaris 10
Posted: Oct 21, 2009 4:19 PM
To: Communities » storage » discuss
Cc: Communities » tools » discuss
Cc: Communities » zfs » discuss
  Click to reply to this thread Reply

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:
root@super01:~# format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
0. c0t5000C5000D34BEDFd0 <SEAGATE-ST31000640SS-0001-931.51GB>
/scsi_vhci/disk@g5000c5000d34bedf
1. c0t5000C5000D34BF37d0 <SEAGATE-ST31000640SS-0001-931.51GB>
/scsi_vhci/disk@g5000c5000d34bf37
2. c0t5000C5000D34C727d0 <SEAGATE-ST31000640SS-0001-931.51GB>
/scsi_vhci/disk@g5000c5000d34c727
3. c0t5000C5000D34D0C7d0 <SEAGATE-ST31000640SS-0001-931.51GB>
/scsi_vhci/disk@g5000c5000d34d0c7
4. c0t5000C5000D34D85Bd0 <SEAGATE-ST31000640SS-0001-931.51GB>
/scsi_vhci/disk@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.

James C. McPher...
jmcp@opensolaris.org
Re: [storage-discuss] Disk locating in OpenSolaris/Solaris 10
Posted: Oct 21, 2009 4:35 PM   in response to: autumnw

  Click to reply to this thread Reply

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:
> root@super01:~# format
> Searching for disks...done
>
>
> AVAILABLE DISK SELECTIONS:
> 0. c0t5000C5000D34BEDFd0 <SEAGATE-ST31000640SS-0001-931.51GB>
> /scsi_vhci/disk@g5000c5000d34bedf
> 1. c0t5000C5000D34BF37d0 <SEAGATE-ST31000640SS-0001-931.51GB>
> /scsi_vhci/disk@g5000c5000d34bf37
> 2. c0t5000C5000D34C727d0 <SEAGATE-ST31000640SS-0001-931.51GB>
> /scsi_vhci/disk@g5000c5000d34c727
> 3. c0t5000C5000D34D0C7d0 <SEAGATE-ST31000640SS-0001-931.51GB>
> /scsi_vhci/disk@g5000c5000d34d0c7
> 4. c0t5000C5000D34D85Bd0 <SEAGATE-ST31000640SS-0001-931.51GB>
> /scsi_vhci/disk@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

If you enabled MPxIO by running /usr/sbin/stmsboot -e, from build
100 onwards, then you should be able to get the information you want
by running

# /usr/sbin/stmsboot -L

example:

$ su root -c ' /usr/sbin/stmsboot -L'
Password:
non-STMS device name STMS device name
------------------------------------------------------------------
/dev/rdsk/c8t0d0 /dev/rdsk/c0t5000C5000EB0DA77d0
/dev/rdsk/c8t7d0 /dev/rdsk/c0t5000C5000EB0DA53d0
/dev/rdsk/c7t4d0 /dev/rdsk/c0t5000C5000B2330F7d0
/dev/rdsk/c7t2d0 /dev/rdsk/c0t5000C5000B21F497d0
/dev/rdsk/c7t11d0 /dev/rdsk/c0t5000C5000A49C693d0
/dev/rdsk/c7t5d0 /dev/rdsk/c0t5000C5000B21F44Fd0
/dev/rdsk/c7t6d0 /dev/rdsk/c0t5000C5000B22864Bd0
/dev/rdsk/c7t9d0 /dev/rdsk/c0t5000C5000B21ABC7d0
/dev/rdsk/c7t8d0 /dev/rdsk/c0t5000C5000B21216Fd0
/dev/rdsk/c7t1d0 /dev/rdsk/c0t5000C5000A4A17DFd0
/dev/rdsk/c7t3d0 /dev/rdsk/c0t5000C5000B21F4E3d0
/dev/rdsk/c7t7d0 /dev/rdsk/c0t5000C5000B20593Fd0
/dev/rdsk/c7t0d0 /dev/rdsk/c0t5000C5000B20566Bd0
/dev/rdsk/c7t10d0 /dev/rdsk/c0t5000C5000A4A17FFd0
/dev/rdsk/c8t1d0 /dev/rdsk/c0t5000C5000EB29213d0
/dev/rdsk/c8t2d0 /dev/rdsk/c0t5000C5000EB15E4Fd0
/dev/rdsk/c8t3d0 /dev/rdsk/c0t5000C5000EB28BEBd0
/dev/rdsk/c8t4d0 /dev/rdsk/c0t5000C5000EB0E2DFd0
/dev/rdsk/c8t5d0 /dev/rdsk/c0t5000C5000EB0D6C3d0
/dev/rdsk/c8t6d0 /dev/rdsk/c0t5000C5000EB2981Fd0


The /usr/lib/scsi/sestopo command might also be useful, if you have
any /dev/es/ses? nodes.

Changes in build 126 (not yet released, though source is available)
will enable you to use cfgadm(1m) for this, too:



lpaso:jmcp $ cfgadm -al c7
Ap_Id Type Receptacle Occupant Condition
c7 scsi-sas connected configured unknown
c7::0,0 disk-path connected configured unknown
c7::1,0 disk-path connected configured unknown
c7::1a,0 disk-path connected configured unknown
c7::1b,0 disk-path connected configured unknown
c7::1c,0 disk-path connected configured unknown
c7::1d,0 disk-path connected configured unknown
c7::1e,0 disk-path connected configured unknown
c7::1f,0 disk-path connected configured unknown
c7::2,0 disk-path connected configured unknown
c7::3,0 disk-path connected configured unknown
c7::4,0 disk-path connected configured unknown
c7::5,0 disk-path connected configured unknown
c7::6,0 disk-path connected configured unknown
c7::7,0 disk-path connected configured unknown
c7::8,0 disk-path connected configured unknown
c7::9,0 disk-path connected configured unknown
c7::10,0 disk-path connected configured unknown
c7::11,0 disk-path connected configured unknown
c7::12,0 disk-path connected configured unknown
c7::13,0 disk-path connected configured unknown
c7::14,0 disk-path connected configured unknown
c7::15,0 disk-path connected configured unknown
c7::16,0 disk-path connected configured unknown
c7::17,0 disk-path connected configured unknown
c7::18,0 disk-path connected configured unknown
c7::19,0 disk-path connected configured unknown
c7::20,0 disk-path connected configured unknown
c7::21,0 disk-path connected configured unknown
c7::22,0 disk-path connected configured unknown
c7::23,0 disk-path connected configured unknown
c7::24,0 disk-path connected configured unknown
c7::25,0 disk-path connected configured unknown
c7::a,0 disk-path connected configured unknown
c7::b,0 disk-path connected configured unknown
c7::e,0 disk-path connected configured unknown
c7::es/ses0 ESI connected configured unknown
c7::es/ses1 ESI connected configured unknown
c7::f,0 disk-path connected configured unknown
c7::smp/expd0 smp connected configured unknown
c7::smp/expd1 smp connected configured unknown


to get the actual SAS WWNs, however, you need to use the 'v' flag,
as well:

elpaso:jmcp $ cfgadm -vla c7
Ap_Id Receptacle Occupant Condition Information
When Type Busy Phys_Id
c7 connected configured unknown
unavailable scsi-sas n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi
c7::0,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000B20566Bd0s0(sd30)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::0,0
c7::1,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000A4A17DFd0s0(sd31)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::1,0
c7::1a,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000288FE43d0s0(sd56)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::1a,0
c7::1b,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000289011Cd0s0(sd57)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::1b,0
c7::1c,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000288FD30d0s0(sd58)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::1c,0
c7::1d,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000288FDFFd0s0(sd59)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::1d,0
c7::1e,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000288FED0d0s0(sd60)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::1e,0
c7::1f,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C500028900EAd0s0(sd61)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::1f,0
c7::2,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000B21F497d0s0(sd32)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::2,0
c7::3,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000B21F4E3d0s0(sd33)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::3,0
c7::4,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000B2330F7d0s0(sd34)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::4,0
c7::5,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000B21F44Fd0s0(sd35)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::5,0
c7::6,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000B22864Bd0s0(sd36)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::6,0
c7::7,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000B20593Fd0s0(sd37)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::7,0
c7::8,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000B21216Fd0s0(sd38)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::8,0
c7::9,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000B21ABC7d0s0(sd39)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::9,0
c7::10,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C500028901F0d0s0(sd46)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::10,0
c7::11,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C50002890131d0s0(sd47)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::11,0
c7::12,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C500028901A4d0s0(sd48)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::12,0
c7::13,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000289012Dd0s0(sd49)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::13,0
c7::14,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000288D828d0s0(sd50)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::14,0
c7::15,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000273A77Cd0s0(sd51)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::15,0
c7::16,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000288FE6Ad0s0(sd52)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::16,0
c7::17,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000288FCF2d0s0(sd53)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::17,0
c7::18,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000288FBE9d0s0(sd54)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::18,0
c7::19,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000288FC1Fd0s0(sd55)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::19,0
c7::20,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000288FC7Fd0s0(sd62)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::20,0
c7::21,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000288FCBDd0s0(sd63)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::21,0
c7::22,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000288FEC0d0s0(sd64)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::22,0
c7::23,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000272E0CBd0s0(sd65)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::23,0
c7::24,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000273018Fd0s0(sd66)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::24,0
c7::25,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000288D566d0s0(sd67)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::25,0
c7::a,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000A4A17FFd0s0(sd40)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::a,0
c7::b,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000A49C693d0s0(sd41)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::b,0
c7::e,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C50002890255d0s0(sd44)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::e,0
c7::es/ses0 connected configured unknown SUN
Storage J4200
unavailable ESI n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::es/ses0
c7::es/ses1 connected configured unknown QUANTA
JS1-10
unavailable ESI n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::es/ses1
c7::f,0 connected configured unknown Client
Device: /dev/dsk/c0t5000C5000289028Ad0s0(sd45)
unavailable disk-path n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::f,0
c7::smp/expd0 connected configured unknown
unavailable smp n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::smp/expd0
c7::smp/expd1 connected configured unknown
unavailable smp n
/devices/pci@0,0/pci8086,3604@1/pci1000,3150@0:scsi::smp/expd1
















--
James C. McPherson
--
Senior Kernel Software Engineer, Solaris
Sun Microsystems
http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog
_______________________________________________
storage-discuss mailing list
storage-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
autumnw

Posts: 11
From:

Registered: 6/30/08
Re: [storage-discuss] Disk locating in OpenSolaris/Solaris 10
Posted: Oct 21, 2009 4:43 PM   in response to: James C. McPher...
To: Communities » storage » discuss
  Click to reply to this thread Reply

Thanks James,

It seems stmsboot does not work with SAS here:
root@super01:~# /usr/sbin/stmsboot -e

WARNING: stmsboot operates on each supported multipath-capable controller
detected in a host. In your system, these controllers are

/pci@0,0/pci8086,340e@7/pci15d9,a580@0
/pci@0,0/pci8086,340c@5/pci1000,3140@0
/pci@0,0/pci8086,340a@3/pci1000,3140@0

If you do NOT wish to operate on these controllers, please quit stmsboot
and re-invoke with -D { fp | mpt } to specify which controllers you wish
to modify your multipathing configuration for.

Do you wish to continue? [y/n] (default: y) y
STMS is already enabled. No changes or reboots needed
root@super01:~# /usr/sbin/stmsboot -L
non-STMS device name STMS device name
------------------------------------------------------------------
root@super01:~# cat /etc/release
OpenSolaris 2009.06 snv_111b X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 07 May 2009
root@super01:~#

BTW, I am using the LSI SAS HBA 3801-E.

James C. McPher...
jmcp@opensolaris.org
Re: [storage-discuss] Disk locating in OpenSolaris/Solaris 10
Posted: Oct 21, 2009 5:10 PM   in response to: autumnw

  Click to reply to this thread Reply

SHOUJIN WANG wrote:
> Thanks James,
>
> It seems stmsboot does not work with SAS here:
> root@super01:~# /usr/sbin/stmsboot -e
>
> WARNING: stmsboot operates on each supported multipath-capable controller
> detected in a host. In your system, these controllers are
>
> /pci@0,0/pci8086,340e@7/pci15d9,a580@0
> /pci@0,0/pci8086,340c@5/pci1000,3140@0
> /pci@0,0/pci8086,340a@3/pci1000,3140@0
>
> If you do NOT wish to operate on these controllers, please quit stmsboot
> and re-invoke with -D { fp | mpt } to specify which controllers you wish
> to modify your multipathing configuration for.
>
> Do you wish to continue? [y/n] (default: y) y
> STMS is already enabled. No changes or reboots needed
> root@super01:~# /usr/sbin/stmsboot -L
> non-STMS device name STMS device name
> ------------------------------------------------------------------

I just found that too, with my system which I've been upgrading
with LU. I know roughly where the problem is, should have a CR
logged for it shortly. In the meantime, you'll have to look at the
output from

$ prtconf -v

for your scsi_vhci devices, and match things up by hand:


Driver properties:
name='inquiry-serial-no' type=string items=1 dev=none
value='000742B94YPC J4V94YPC'
...
name='compatible' type=string items=4
value='scsiclass,00.vHITACHI.pHUS1514SBSUN146G.rSA02' +
'scsiclass,00.vHITACHI.pHUS1514SBSUN146G' + 'scsiclass,00' + 'scsiclass'
name='client-guid' type=string items=1
value='5000cca00510a7cc'
Paths from multipath bus adapters:
Path 1: /pci@0,0/pci10de,376@a/pci1000,3150@0/disk@0,0
mpt#0 (online)
name='wwn' type=string items=1
value='5000cca00510a7cc'
name='target' type=int items=1
value=00000000
name='lun' type=int items=1
value=00000000
name='target-port' type=string items=1
value='5000cca00510a7cd'
name='path-class' type=string items=1
value='primary'

The above info tells me that this disk under scsi_vhci will have
5000CCa00510A7CD in the 't' part of the name, that it's physically
attached to my mpt0 instance, and that it's target 0 lun 0 on
that controller.



James C. McPherson
--
Senior Kernel Software Engineer, Solaris
Sun Microsystems
http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog
_______________________________________________
storage-discuss mailing list
storage-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
James C. McPher...
jmcp@opensolaris.org
Re: [storage-discuss] Disk locating in OpenSolaris/Solaris 10
Posted: Oct 21, 2009 5:18 PM   in response to: James C. McPher...

  Click to reply to this thread Reply


Sorry, forgot - there's another way you can fill the gap:

$ ls -l /dev/dsk/*5000CCA00510A7CCd0s2
lrwxrwxrwx 1 root root 48 Nov 20 2008
/dev/dsk/c4t5000CCA00510A7CCd0s2 ->
../../devices/scsi_vhci/disk@g5000cca00510a7cc:c


# /lib/mpxio/stmsboot_util -p /scsi_vhci/disk@g5000cca00510a7cc:a
/pci@0,0/pci10de,376@a/pci1000,3150@0/sd@0,0:a


cheers,
James C. McPherson
--
Senior Kernel Software Engineer, Solaris
Sun Microsystems
http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog
_______________________________________________
storage-discuss mailing list
storage-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
autumn

Posts: 3
From: US

Registered: 10/30/09
Re: [storage-discuss] Disk locating in OpenSolaris/Solaris 10
Posted: Nov 3, 2009 3:03 PM   in response to: James C. McPher...
To: Communities » storage » discuss
Cc: OpenSolaris » discuss
  Click to reply to this thread Reply

It is very useful James.

BTW, I also found another open source which can blink disk:
http://sg.danny.cz/sg/sdparm.html

Another question I have is: When I add a new disk (hot-plugin), it seems it will not be mapped automaticly. It seems I have to do "stmsboot -d" and "stmsboot -e". That means I need to reboot the server for two times. Is there anyway to have the mapping happen without rebooting?

root@super01:/lib/mpxio# ./stmsboot_util -m c12t6d0
NOT_MAPPED

Regards,
Autumn Wang.
~~~~~~~~~~~~~

James C. McPher...
jmcp@opensolaris.org
Re: [storage-discuss] Disk locating in OpenSolaris/Solaris 10
Posted: Nov 3, 2009 3:07 PM   in response to: autumn

  Click to reply to this thread Reply

autumn Wang wrote:
> It is very useful James.
>
> BTW, I also found another open source which can blink disk:
> http://sg.danny.cz/sg/sdparm.html
>
> Another question I have is: When I add a new disk (hot-plugin), it seems it will not be mapped automaticly. It seems I have to do "stmsboot -d" and "stmsboot -e". That means I need to reboot the server for two times. Is there anyway to have the mapping happen without rebooting?
>
> root@super01:/lib/mpxio# ./stmsboot_util -m c12t6d0
> NOT_MAPPED

Hi Autumn,
in order for your new disk to be visible to the system,
you need to configure it in, using cfgadm

# cfgadm -c configure c12

It is possible that you might also need to run

# devfsadm -i sd


Please see the cfgadm(1m) and devfsadm(1m) manpages.


What I expect to happen with /usr/sbin/stmsboot is that
this new disk should show up in the output from

# /usr/sbin/stmsboot -L


Please remember that /lib/mpxio/stmsboot_util is *not* a
utility that people are supposed to run by themselves, it
is a private utility for the use of /usr/sbin/stmsboot.


James C. McPherson
--
Senior Kernel Software Engineer, Solaris
Sun Microsystems
http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog
_______________________________________________
storage-discuss mailing list
storage-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Point your RSS reader here for a feed of the latest messages in all forums
Go Back Back to Thread List



Terms of Use | Privacy | Trademarks | Copyright Policy | Site Guidelines
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Use.
Copyright © 1995-2005 Sun Microsystems, Inc.