hyperic-hq-discuss

[Hyperic-hq-discuss] Does SIGAR support Solaris Volume Manager?

[JeanDagenais2 <sig...@hy...>]

I have built an agent to collect OS information from different platforms, and on our Solaris/Sparc platform, I can't get all the iostat information about disks.

I am not sure if this is a limitation because of the Solaris volume manager, or something else....

For example, this is what we get back:

srv0112101 $java -jar sigar.jar        
sigar> iostat
Filesystem      Mounted on           Reads     Writes R-bytes W-bytes Queue Svctm
/dev/md/dsk/d0  /                       -1         -1       -       -     -     -
/dev/md/dsk/d5  /usr                    -1         -1       -       -     -     -
/dev/md/dsk/d4  /var                    -1         -1       -       -     -     -
/dev/md/dsk/d3  /home                   -1         -1       -       -     -     -
/dev/md/dsk/d6  /opt                    -1         -1       -       -     -     -
/dev/dsk/c1t1d0s6 /apps               288238    1904778    5.6G     28G  0.00 17.44
/dev/dsk/c1t1d0s3 /app-backup         -1         -1       -       -     -     -
sigar> 


srv0112101 $iostat -PmXn
                    extended device statistics              
    r/s    w/s   kr/s   kw/s wait actv wsvc_t asvc_t  %w  %b device
    0.0    0.1    0.5    1.7  0.0  0.0    0.0   12.4   0   0 c1t0d0s0
    0.0    0.0    0.7    0.0  0.0  0.0    0.0    0.3   0   0 c1t0d0s1
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.4   0   0 c1t0d0s2
    0.0    0.0    0.2    0.1  0.0  0.0    0.0    8.6   0   0 c1t0d0s3
    0.1    0.7    2.7    4.8  0.0  0.0    0.0    8.7   0   0 c1t0d0s4
    0.1    0.0    1.8    0.2  0.0  0.0    0.0    4.6   0   0 c1t0d0s5
    0.0    0.0    0.8    0.1  0.0  0.0    0.0    7.0   0   0 c1t0d0s6
    0.0    0.6    0.0    0.3  0.0  0.0    0.0   13.7   0   0 c1t0d0s7
    0.0    0.0    0.0    0.0  0.0  0.0    0.0   20.1   0   0 c1t1d0s0
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.3   0   0 c1t1d0s1
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.4   0   0 c1t1d0s2
    0.0    0.0    0.1    0.6  0.0  0.0    0.1   17.4   0   0 c1t1d0s6 (/apps)
    0.0    0.0    0.1    0.6  0.0  0.0    0.0    7.4   0   0 c2t8d0s0
    0.0    0.0    0.0    0.7  0.0  0.0    0.0    6.4   0   0 c2t8d0s1
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.0   0   0 c2t8d0s2
    0.0    0.0    0.0    0.3  0.0  0.0    0.0    9.1   0   0 c2t8d0s3
    0.0    0.3    0.0    2.8  0.0  0.0    0.0    7.4   0   0 c2t8d0s4
    0.0    0.0    0.6    0.8  0.0  0.0    0.0    5.3   0   0 c2t8d0s5
    0.0    0.0    0.3    0.6  0.0  0.0    0.0    8.7   0   0 c2t8d0s6
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    4.9   0   0 c2t8d0s7
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.0   0   0 c2t9d0s0
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.0   0   0 c2t9d0s1
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.0   0   0 c2t9d0s2
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.0   0   0 c2t9d0s6
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.1   0   0 srv0112101:vold(pid406)
    3.5    0.3   20.6    1.9  0.0  0.0    0.1    2.2   0   1 srv0112002a:/vol/vAppl

Re: [Hyperic-hq-discuss] Does SIGAR support Solaris Volume Manager?

[Doug M. <do...@hy...>]

We have a challenge with mapping the file system mount point (e.g. /usr) to the kstat name used to collect the iostats.  We use code rather than the actual commands listed below, but the mapping is done like this:

First the device name:
% df /
/ (/dev/dsk/c3t0d0s0 ): 2065804 blocks 1019523 files

% ls -l /dev/dsk/c3t0d0s0
lrwxrwxrwx 1 root root 65 Dec 27 2005 /dev/dsk/c3t0d0s0 -> ../../devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0:a

strip "../../devices" and trailing ":%c" which is the partition

% grep /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0 /etc/path_to_inst
"/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0" 3 "sd"

Gives us the 3 pieces ("sd", 3, "a") needed to get the metrics using the kstat api:

% kstat -n sd3,a
module: sd instance: 3
name: sd3,a class: partition
crtime 171.04862756
nread 923651720
...

This code was written before opensolaris was available.. I just had a look at how the iostat command maps the kstat name to disk name when you specify the -n switch, it's not pretty.
If anybody knows a simple way to do this mapping, I'd be happy to hear about it!

You can use the device name displayed by iostat (w/o the -n switch), for example 'sd1' with Sigar.getDiskUsage("sd1").  You'll see the same list of names with: kstat -c disk
We also plan to implement an API to get the list of disks: http://jira.hyperic.com/browse/SIGAR-113