really heavy asvc_t
in [Solaris]
|
Prev: strccpy
Next: NBA listing on Satellite
From: martin on 4 Jun 2010 16:31 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
From: Scott on 6 Jun 2010 22:43 On Jun 4, 1:31 pm, martin <marcin.jarosin...(a)gmail.com> wrote: > 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 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.
From: martin on 7 Jun 2010 11:44 On Jun 6, 10:43 pm, Scott <spack...(a)gmail.com> wrote: > On Jun 4, 1:31 pm, martin <marcin.jarosin...(a)gmail.com> wrote: > > > > > 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 > > 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. 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 Ive 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
From: Voropaev Pavel on 8 Jun 2010 08:33 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 pm, Scott <spack...(a)gmail.com> wrote: > > On Jun 4, 1:31 pm, martin <marcin.jarosin...(a)gmail.com> wrote: > > > > > > > > > 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 > > > > 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. > > 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 Ive 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
|
Pages: 1 Prev: strccpy Next: NBA listing on Satellite |