[Orca-users] Re: Seeing Only one Disk

[Blair Zajac]

"Phillip B. Bruce" wrote:
> 
> Blair Zajac wrote:
> 
> > "Phillip B. Bruce" wrote:
> > >
> > > Blair,
> > >
> > >       The Disk Run Percent [Info]  only shows c1t1d0 when I have
> > lots
> > > more than this.
> > >
> > >       See Below:
> > >
> > >      % df -k
> > > Filesystem            kbytes    used   avail capacity  Mounted on
> > > /dev/dsk/c0d0s0       288256   30817  228614    12%    /
> > > /dev/dsk/c0d0s6      1485664  527664  898574    37%    /usr
> > > /dev/dsk/c0d0p0:boot   10391    1623    8767    16%    /boot
> > > /proc                      0       0       0     0%    /proc
> > > fd                         0       0       0     0%    /dev/fd
> > > mnttab                     0       0       0     0%    /etc/mnttab
> > > /dev/dsk/c0d0s4       240023   78361  137660    37%    /var
> > > swap                  482280       4  482276     1%    /var/run
> > > swap                  483368    1092  482276     1%    /tmp
> > > /dev/dsk/c0d0s3       650582  175588  416442    30%    /opt
> > > /dev/dsk/c0d1s0      2052750 1762916  228252    89%    /u01
> > > /dev/dsk/c0d1s3      2052750  979754 1011414    50%    /web
> > > /dev/dsk/c0d1s4      2052750  420300 1570868    22%    /u02
> > > /dev/dsk/c1d0s7       858015  778326   19628    98%    /software
> > > /dev/dsk/c0d1s1      2052750  865973 1125195    44%    /opt/sfw
> > > /dev/dsk/c0d0s7       960702  479060  424000    54%    /export/home
> > > /dev/dsk/c1d0s6       963183  910955       0   100%    /usr/local
> > >
> > > While the others:
> > > Disk System Wide Reads/Writes Per Second [Info]
> > > Disk System Wide Transfer Rate [Info]
> > > Disk Space Percent Usage [Info]
> > > Disk Inode Percent Usage [Info]
> > >
> > > They report everything there but I'm skeptical of the Disk System
> > Wide
> > > Read/Writes Per Second
> > >   being correct or the System Wide Transfer. The Sparc Percent Usage
> > and
> > > Inode Percent Usage
> > >   is being reported correct. I should be seeing more. Is there a new
> >
> > > patch for this problem.
> > >
> > > I'm running this version
> > > orca -v lib/orcallator.cfg
> > > Orca version 0.264
> > >
> >
> > Check your percol-* output files and see how many column names begin
> > with
> > disk_runp_.  Is it just the one or are there more?
> >
> > You're running x86 Solaris, right?  I don't see a c1t1d0 disk in your
> > df -k output.  Is this filesystem on another system?
> >
> > It looks like the regular expression for matching this is in
> > orcallator.cfg
> > does not match for these filesystems:
> >
> >     data   disk_runp_((?:c\d+t\d+d\d+)|(?:[ms]d\d+))
> >
> > It should be changed to something like
> >
> >     data   disk_runp_((?:c\d+t\d+d\d+)|(?:c\d+d\d+s\d+)|(?:[ms]d\d+))
> >
> > Try this and let me know if it works.
> >
> > The Disk System Wide Read/Writes Per Second and the System Wide
> > Transfer
> > rate could be wrong if not all of the disks are seen in the percol-*
> > output files.  However, if they are there, then these other
> > measurements
> > should be correct.
> >
> > I just logged into an x86 Solaris box and it had filesystems mounted
> > like
> >       /dev/dsk/c0t0d0s3    1015874  244623  761093    25%    /var
> > which is the same for Sparc Solaris.  Do you know why the device names
> >
> > are different from the x86 system I looked at?
> >
> > Blair
> >
> 
> Blair,
> 
>    I cut and paste the info you requested in the orcallator.cfg file.
>    I stop and restarted the orcallator and it still didn't get it.
> 
>    Keep in mind your x86 may be just all SCSI disks. That why it
> captured the SCSI cdrom burner
>    on my system. The rest of the drives are IDE. That is why they look
> funny in the df -k output.
>    Now you know why there isn't a SCSI target number.
> 
>    Here is my rrd output:
> 
>   ls *disk*
> gauge_1024_X_disk_rK_per_s.rrd  gauge_disk_runp_c1t1d0.rrd
> gauge_1024_X_disk_wK_per_s.rrd  gauge_disk_wr_per_s.rrd
> gauge_disk_rd_per_s.rrd
> 
>    As you can see it still only see that c1t1d0 drive.

Phillip,

Check the percol-* files, not the RRD files, for all of the column names
that contain disk_runp_*.  The RRD files are only generated by Orca if Orca's
configuration file finds the columns it is instructed to in the percol-*
files.

Blair

-- 
Blair Zajac <blair at orcaware.com> - Perl & sysadmin services for hire
OS & web analysis - http://www.orcaware.com/orca/