Following is a result of iostat -dnxc on my dev box running solaris 10
(sparc).  Please note that i'm a DBA and have been deprived of a UNIX
admin so if this is a RTFM question please do not hesitate to tell me.

This is a system with a single database that's really not generating
that much volume.


     cpu
 us sy wt id
  0  0  0 100
                    extended device statistics
    r/s    w/s   kr/s   kw/s wait actv wsvc_t asvc_t  %w  %b device
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.0   0   0 c0t1d0
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.0   0   0 c0t0d0
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.0   0   0 c0t3d0
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.0   0   0
c2t207000C0FFDA4745d0
    1.0    0.0   12.0    0.0  0.0 38.7    0.0 38719.4   0 100
c1t247000C0FFDA4745d0
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.0   0   0
dlsndb01:vold(pid488)


In short, what can cause this kind of craziness? ... any and all input
is appreciated.

Martin

On Jun 4, 1:31=A0pm, martin <marcin.jarosin...@gmail.com> wrote:
> Following is a result of iostat -dnxc on my dev box running solaris 10
> (sparc). =A0Please note that i'm a DBA and have been deprived of a UNIX
> admin so if this is a RTFM question please do not hesitate to tell me.
>
> This is a system with a single database that's really not generating
> that much volume.
>
> =A0 =A0 =A0cpu
> =A0us sy wt id
> =A0 0 =A00 =A00 100
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 extended device statistics
> =A0 =A0 r/s =A0 =A0w/s =A0 kr/s =A0 kw/s wait actv wsvc_t asvc_t =A0%w =
=A0%b device
> =A0 =A0 0.0 =A0 =A00.0 =A0 =A00.0 =A0 =A00.0 =A00.0 =A00.0 =A0 =A00.0 =A0=
 =A00.0 =A0 0 =A0 0 c0t1d0
> =A0 =A0 0.0 =A0 =A00.0 =A0 =A00.0 =A0 =A00.0 =A00.0 =A00.0 =A0 =A00.0 =A0=
 =A00.0 =A0 0 =A0 0 c0t0d0
> =A0 =A0 0.0 =A0 =A00.0 =A0 =A00.0 =A0 =A00.0 =A00.0 =A00.0 =A0 =A00.0 =A0=
 =A00.0 =A0 0 =A0 0 c0t3d0
> =A0 =A0 0.0 =A0 =A00.0 =A0 =A00.0 =A0 =A00.0 =A00.0 =A00.0 =A0 =A00.0 =A0=
 =A00.0 =A0 0 =A0 0
> c2t207000C0FFDA4745d0
> =A0 =A0 1.0 =A0 =A00.0 =A0 12.0 =A0 =A00.0 =A00.0 38.7 =A0 =A00.0 38719.4=
 =A0 0 100
> c1t247000C0FFDA4745d0
> =A0 =A0 0.0 =A0 =A00.0 =A0 =A00.0 =A0 =A00.0 =A00.0 =A00.0 =A0 =A00.0 =A0=
 =A00.0 =A0 0 =A0 0
> dlsndb01:vold(pid488)
>
> In short, what can cause this kind of craziness? ... any and all input
> is appreciated.
>
> Martin

The command gives counts since the system was last booted, which you
probably
don't want nor care too much about.
Try: iostat -dnxc 10
and ignore the first results returned.  The next result returned will
be the iostat
within the 10 seconds that have elapsed.  Watch it for a couple of
minutes.

On Jun 6, 10:43=A0pm, Scott <spack...@gmail.com> wrote:
> On Jun 4, 1:31=A0pm, martin <marcin.jarosin...@gmail.com> wrote:
>
>
>
> > Following is a result of iostat -dnxc on my dev box running solaris 10
> > (sparc). =A0Please note that i'm a DBA and have been deprived of a UNIX
> > admin so if this is a RTFM question please do not hesitate to tell me.
>
> > This is a system with a single database that's really not generating
> > that much volume.
>
> > =A0 =A0 =A0cpu
> > =A0us sy wt id
> > =A0 0 =A00 =A00 100
> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 extended device statistics
> > =A0 =A0 r/s =A0 =A0w/s =A0 kr/s =A0 kw/s wait actv wsvc_t asvc_t =A0%w =
=A0%b device
> > =A0 =A0 0.0 =A0 =A00.0 =A0 =A00.0 =A0 =A00.0 =A00.0 =A00.0 =A0 =A00.0 =
=A0 =A00.0 =A0 0 =A0 0 c0t1d0
> > =A0 =A0 0.0 =A0 =A00.0 =A0 =A00.0 =A0 =A00.0 =A00.0 =A00.0 =A0 =A00.0 =
=A0 =A00.0 =A0 0 =A0 0 c0t0d0
> > =A0 =A0 0.0 =A0 =A00.0 =A0 =A00.0 =A0 =A00.0 =A00.0 =A00.0 =A0 =A00.0 =
=A0 =A00.0 =A0 0 =A0 0 c0t3d0
> > =A0 =A0 0.0 =A0 =A00.0 =A0 =A00.0 =A0 =A00.0 =A00.0 =A00.0 =A0 =A00.0 =
=A0 =A00.0 =A0 0 =A0 0
> > c2t207000C0FFDA4745d0
> > =A0 =A0 1.0 =A0 =A00.0 =A0 12.0 =A0 =A00.0 =A00.0 38.7 =A0 =A00.0 38719=
..4 =A0 0 100
> > c1t247000C0FFDA4745d0
> > =A0 =A0 0.0 =A0 =A00.0 =A0 =A00.0 =A0 =A00.0 =A00.0 =A00.0 =A0 =A00.0 =
=A0 =A00.0 =A0 0 =A0 0
> > dlsndb01:vold(pid488)
>
> > In short, what can cause this kind of craziness? ... any and all input
> > is appreciated.
>
> > Martin
>
> The command gives counts since the system was last booted, which you
> probably
> don't want nor care too much about.
> Try: iostat -dnxc 10
> and ignore the first results returned. =A0The next result returned will
> be the iostat
> within the 10 seconds that have elapsed. =A0Watch it for a couple of
> minutes.

Hey Scott,

First, thank you for replying!

The results of the iostat -dnxc I posted was not the fist one, when I
got the particular one I=92ve been monitoring the server for a few
hours.  Basically I should have mentioned I user iostat -dnxc 3 to
obtain the results and it was not the first result I used.

Martin

Drive looks like LUN. So, guess it is some problems with SAN or LUN,
or maybe multipathing.
if you using native mulipath support try
mpathadm show lu /dev/rdsk/c2t207000C0FFDA4745d0

case of veritas
vxdisk list
vxdisk list <entry for your drive from previos command>
What server model?


martin wrote:
> On Jun 6, 10:43=A0pm, Scott <spack...@gmail.com> wrote:
> > On Jun 4, 1:31=A0pm, martin <marcin.jarosin...@gmail.com> wrote:
> >
> >
> >
> > > Following is a result of iostat -dnxc on my dev box running solaris 1=
0
> > > (sparc). =A0Please note that i'm a DBA and have been deprived of a UN=
IX
> > > admin so if this is a RTFM question please do not hesitate to tell me=
..
> >
> > > This is a system with a single database that's really not generating
> > > that much volume.
> >
> > > =A0 =A0 =A0cpu
> > > =A0us sy wt id
> > > =A0 0 =A00 =A00 100
> > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 extended device statistics
> > > =A0 =A0 r/s =A0 =A0w/s =A0 kr/s =A0 kw/s wait actv wsvc_t asvc_t =A0%=
w =A0%b device
> > > =A0 =A0 0.0 =A0 =A00.0 =A0 =A00.0 =A0 =A00.0 =A00.0 =A00.0 =A0 =A00.0=
 =A0 =A00.0 =A0 0 =A0 0 c0t1d0
> > > =A0 =A0 0.0 =A0 =A00.0 =A0 =A00.0 =A0 =A00.0 =A00.0 =A00.0 =A0 =A00.0=
 =A0 =A00.0 =A0 0 =A0 0 c0t0d0
> > > =A0 =A0 0.0 =A0 =A00.0 =A0 =A00.0 =A0 =A00.0 =A00.0 =A00.0 =A0 =A00.0=
 =A0 =A00.0 =A0 0 =A0 0 c0t3d0
> > > =A0 =A0 0.0 =A0 =A00.0 =A0 =A00.0 =A0 =A00.0 =A00.0 =A00.0 =A0 =A00.0=
 =A0 =A00.0 =A0 0 =A0 0
> > > c2t207000C0FFDA4745d0
> > > =A0 =A0 1.0 =A0 =A00.0 =A0 12.0 =A0 =A00.0 =A00.0 38.7 =A0 =A00.0 387=
19.4 =A0 0 100
> > > c1t247000C0FFDA4745d0
> > > =A0 =A0 0.0 =A0 =A00.0 =A0 =A00.0 =A0 =A00.0 =A00.0 =A00.0 =A0 =A00.0=
 =A0 =A00.0 =A0 0 =A0 0
> > > dlsndb01:vold(pid488)
> >
> > > In short, what can cause this kind of craziness? ... any and all inpu=
t
> > > is appreciated.
> >
> > > Martin
> >
> > The command gives counts since the system was last booted, which you
> > probably
> > don't want nor care too much about.
> > Try: iostat -dnxc 10
> > and ignore the first results returned. =A0The next result returned will
> > be the iostat
> > within the 10 seconds that have elapsed. =A0Watch it for a couple of
> > minutes.
>
> Hey Scott,
>
> First, thank you for replying!
>
> The results of the iostat -dnxc I posted was not the fist one, when I
> got the particular one I=92ve been monitoring the server for a few
> hours.  Basically I should have mentioned I user iostat -dnxc 3 to
> obtain the results and it was not the first result I used.
>
> Martin