10-08-2009
Hey thanks man. It worked out. I mean i ran 7 dd commands and finally i saw my wait queue value going up. but the tool sunvts has a lot to be desired still. But anyway. alls well that ends well.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi all,
i have run iostat -em, and get below result. Can i know what is this output meaning, and how to fix that problem.
iostat -em
---- errors ---
device s/w h/w trn tot
sd7 0 1 0 1
sd8 1 1 0 2
sd9 0 1 0 1
sd10 0 ... (2 Replies)
Discussion started by: foongkt5220
2 Replies
2. Filesystems, Disks and Memory
All,
I am attempting to help tune a Sun for better performance (mainly for SAS 9.1), and have found indicators pointing to poor I/O utilization. I have run iostat -cx, and found one device in particular where the %w is in the 90's during processing. I have a feeling that this is where the SAS... (3 Replies)
Discussion started by: dj_is
3 Replies
3. AIX
Hi All AIX expert
i'm using AIX 5.2
When i execute this command which is :
----------------------------------------------------------------------
>> iostat -a
System configuration: lcpu=4 disk=30
tty: tin tout avg-cpu: % user % sys % idle % iowait
... (2 Replies)
Discussion started by: adzuanamir
2 Replies
4. Shell Programming and Scripting
bash-3.00# ./test.sh 100 10
./test.sh: syntax error at line 6: `(' unexpected
bash-3.00# cat test.sh
#!/bin/sh
start=0
end=$1
interval=$2
iostat -xnpr > disk_iostats.csv
for (( start=0; $start<=$end; start=$(($start+$interval)) ))
do
sleep $interval
iostat -xnpr | grep -v device >>... (0 Replies)
Discussion started by: ilan
0 Replies
5. Solaris
Sorry for asking basics. What exactly is the situation if device ID is same in iostat -Eni. What we must do then? Is there any relation b/w iostat and cfgadm? (3 Replies)
Discussion started by: mayahari
3 Replies
6. Red Hat
A find for the "iostat" command on a redhat 5 update 4 comes back with no results.
Any separate rpm needs to be installed to get the binary for this ?
Thanks in advance. (1 Reply)
Discussion started by: uxadmin007
1 Replies
7. Solaris
I all,
I would like to know what are the causes of :
-soft error
-harderror
-transport error
and how to avoid and repare them.
I got the iostat out put below:
atng-mm01% iostat -En | grep -i hard
c0t0d0 Soft Errors: 1 Hard Errors: 0 Transport Errors: 0
c0t0d1 ... (3 Replies)
Discussion started by: zaza
3 Replies
8. Shell Programming and Scripting
Does anyone have an example of IOSTAT -eE in a script???????
Need to see the syntax in a script (4 Replies)
Discussion started by: walnutpony123
4 Replies
9. Solaris
Hello everyone,
Can you please explain me what kind of information do IOSTAT show ?
iostat -xnz 3 show me those informations:
The I/O of the c0t0d0 disk is normal ?
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 ... (3 Replies)
Discussion started by: adilyos
3 Replies
10. AIX
Hello, I support Oracle 11g on AIX 7.1.
Using the command
$iostat -D hdisk2 hdisk4 hdisk5 5
I get the following output:
hdisk5 xfer: %tm_act bps tps bread bwrtn
44.0 1.4M 178.2 1.4M 14.7K
read: ... (3 Replies)
Discussion started by: oracledba1024
3 Replies
LEARN ABOUT POSIX
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.10 1 Mar 1994 queuedefs(4)