Platform: Sun Solaris ver 9.
Get alert notification from Oracle and the device stated: Disk utilization for ssd29 reached 98%. How can we map this ssd device with something like c1t2d0s0?
Pls help. Thank you.
Platform: Sun Solaris ver 9.
Get alert notification from Oracle and the device stated: Disk utilization for ssd29 reached 98%. How can we map this ssd device with something like c1t2d0s0?
Pls help. Thank you.
have a look at the "metastat -p" output.
encountered error ..:o
# metastat -p
metastat: hostname: there are no existing databases
Try to find it under the /dev hierarchy.
find /dev -name ssd2*
No result return from below command..
# find /dev -name ssd*
#
Maybe if it was d29 , not ssd29
You can use format
ie:
From messages file
/var/adm/messages.1:Feb 11 10:19:22 xxxxxxxxx genunix: [ID 936769 kern.info] ssd4 is /scsi_vhci/ssd@g60060e80047f150000007f1500000325
So lets look for ssd4
From format
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> root-pri
/pci@1c,600000/scsi@2/sd@0,0
1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> root-sec
/pci@1c,600000/scsi@2/sd@1,0
2. c5t60060E80047F150000007F1500000321d0 <HITACHI-OPEN-V-SUN-5009 cyl 9555 alt 2 hd 15 sec 512>
/scsi_vhci/ssd@g60060e80047f150000007f1500000321
3. c5t60060E80047F150000007F1500000322d0 <HITACHI-OPEN-V-SUN-5009 cyl 9555 alt 2 hd 15 sec 512>
/scsi_vhci/ssd@g60060e80047f150000007f1500000322
4. c5t60060E80047F150000007F1500000325d0 <HITACHI-OPEN-V-SUN-5009 cyl 9555 alt 2 hd 15 sec 512>
/scsi_vhci/ssd@g60060e80047f150000007f1500000325
5. c5t60060E80047F150000007F1500000326d0 <HITACHI-OPEN-V-SUN-5009 cyl 9555 alt 2 hd 15 sec 512>
/scsi_vhci/ssd@g60060e80047f150000007f1500000326
Specify disk (enter its number):
If you don't have any entries in your messages files you can look in /etc/path_to_inst
# grep ssd /etc/path_to_inst
"/scsi_vhci/ssd@g60060e80047f150000007f1500000325" 4 "ssd"
"/scsi_vhci/ssd@g60060e80047f150000007f1500000326" 5 "ssd"
"/scsi_vhci/ssd@g60060e80047f150000007f1500000321" 6 "ssd"
"/scsi_vhci/ssd@g60060e80047f150000007f1500000322" 7 "ssd"
"/pci@1d,700000/SUNW,qlc@1/fp@0,0/ssd@w50060e80047f1544,0" 2 "ssd"
"/pci@1d,700000/SUNW,qlc@1/fp@0,0/ssd@w50060e80047f1524,0" 3 "ssd"
"/pci@1d,700000/SUNW,qlc@1,1/fp@0,0/ssd@w50060e80047f1554,0" 0 "ssd"
"/pci@1d,700000/SUNW,qlc@1,1/fp@0,0/ssd@w50060e80047f1534,0" 1 "ssd"
#
And then:
ls -l /dev/dsk | fgrep "/scsi_vhci/ssd@g60060e80047f150000007f1500000325"
You don't need to do that as you already know which disk it is from the format command..
In my example it is /dev/dsk/c5t60060E80047F150000007F1500000325d0
If SVM was used then you would need to go one step further.
# metastat -p
d30 -m d31 d32 1
d31 1 1 c1t0d0s3
d32 1 1 c1t1d0s3
d10 -m d11 d12 1
d11 1 1 c1t0d0s0
d12 1 1 c1t1d0s0
d20 -m d21 d22 1
d21 1 1 c1t0d0s1
d22 1 1 c1t1d0s1
d50 -m d51 d52 1
d51 1 1 c1t0d0s5
d52 1 1 c1t1d0s5
d215 -p d210 -o 7808 -b 144703488
d210 -m d211 1
d211 1 2 /dev/dsk/c5t60060E80047F150000007F1500000321d0s0 /dev/dsk/c5t60060E80047F150000007F1500000322d0s0 -i 128b
d204 -p d200 -o 104865440 -b 39845888
d200 1 2 /dev/dsk/c5t60060E80047F150000007F1500000325d0s0 /dev/dsk/c5t60060E80047F150000007F1500000326d0s0 -i 32b
d202 -p d200 -o 20979264 -b 41943040
d201 -p d200 -o 7712 -b 20971520 -o 62922336 -b 20971520
#
So in my example there are soft partitions sitting on this SAN disk
Thay are d201 d202 and d204 which are mounted as:
/dev/md/dsk/d201 20G 15G 4.4G 78% /export/install
/dev/md/dsk/d202 20G 4.7G 15G 24% /export/patches
/dev/md/dsk/d204 19G 3.6G 15G 20% /var/www
So ssd4 is split into 3 softpartitions mounted as above.
Sure... I just find it quicker on systems with very large numbers of attached disks, where format can take some time to run.
True......