03-04-2005
iostat -E and -e seems to be more applicable to olden days of pure HDDs.
With SAN and RAID , I dun think it's relevant anymore.
9 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. AIX
Can someone tell me what the output of 'who -d' is ?
What's causing the process in the list to be there ?
What can be done to get rid of / fix those process ?
Are those process simple problems, important or urgent onces ?
I am asking because while looking for another 'who' option, I... (2 Replies)
Discussion started by: Browser_ice
2 Replies
3. Shell Programming and Scripting
So I use Cacti for monitoring IO statistics on my servers, now originally I couldnt monitor Multipath deviced servers as they have alot of /dev/sdxx and /dev/emcpowerxx, I have devised a method of trimming them down to just the actual devices but the issue is the output looks like so.
# iostat... (0 Replies)
Discussion started by: RiSk
0 Replies
4. Shell Programming and Scripting
Friends,
.
On linux i have to run iostat command and in each iteration have to print the greatest value in each column.
e.g
iostat -dt -kx 2 2 | awk ' !/sd/ &&!/%util/ && !/Time/ && !/Linux/ {print $12}'
4.38
0.00
0.00
0.00
What i would like to print is only the... (3 Replies)
Discussion started by: achak01
3 Replies
5. Shell Programming and Scripting
Friends,
Need some help.
On linux i have to run iostat command and in each iteration have to print the greatest value in each column.
e.g
iostat -dt -kx 2 2 | awk ' !/sd/ &&!/%util/ && !/Time/ && !/Linux/ {print $12}'
4.38
0.00
0.00
0.00
WHhat i would like to... (15 Replies)
Discussion started by: achak01
15 Replies
6. Filesystems, Disks and Memory
Hi Guys,
I've been having some arguments with my colleagues about one thing. Always my thought was that as as far as disk performance is concern by looking at the output of the iostat command (AIX) you would be able to identify if you have a hot disk and then by moving some files out that disk... (3 Replies)
Discussion started by: arizah
3 Replies
7. Solaris
My scheduled collection of statistics is giving very large output because of an high number of ssd device not associated to any disk
The iostat -x command is collecting statistics from them and the output is very large.
I.g.
if a run
iostat -x|tail +3|awk '{print $1}'>f0.txt.$$
iostat... (5 Replies)
Discussion started by: sun-mik
5 Replies
8. Solaris
Noticed that asvc_t values in iostat command outputs are mostly more than 100 in our previous iostat analysis.
Also found the following detail from an alternate site IO Bottleneck - Disk performance issue - UnixArena
----
1. asvc_t average service time of active transactions, in... (2 Replies)
Discussion started by: saraperu
2 Replies
9. Shell Programming and Scripting
Hi,
I got the code below is one of the threads from this forum.
lineCount=$(iostat | wc -l)
numDevices=$(expr $lineCount - 7);
iostat $interval -x -t |
awk -v awkCpuFile=$cpuFile -v awkDeviceFile=$deviceFile -v awkNumDevices=$numDevices '
BEGIN {
print... (2 Replies)
Discussion started by: gopivallabha
2 Replies
LEARN ABOUT HPUX
pthread_set_nice_np
pthread_get_nice_np(3T) pthread_get_nice_np(3T)
NAME
pthread_get_nice_np(), pthread_set_nice_np() - get or set the nice value of a thread
SYNOPSIS
PARAMETERS
thread The thread whose nice value is to be set/retrieved.
nice_val Value of nice to be applied to the target thread is returned (get function) or it specifies the new value of nice for
thread (set function).
DESCRIPTION
These functions are used to set and retrieve the nice value of an individual thread.
returns the current nice value setting of the target thread and stores it in nice_val. adds the value of nice_val to the current nice
value of the target thread.
A thread's nice value is a non-negative number. The system imposes a minimum nice value of 0 and a maximum of 39 with lower nice values
providing more favorable scheduling. If calling results in a nice value outside the range of 0 to 39, the value will be set to the nearest
limit. A process must have appropriate privileges to lower a thread's nice value. The function allows individual threads in the process
to have different nice values.
returns the current nice value less 20 and will be in the range -20 to +19.
The nice value of only system scope threads can be changed. An attempt to change the nice value of a process-scope thread will result in a
return value of Calling on a thread that has a scheduling policy other than will have an effect only when the thread's scheduling policy
changes to If a thread calls the system call to create a new process, the new process inherits the process-level nice value. Calling to
create a new thread will result in the new thread inheriting the creating thread's nice value.
Note
If the nice value of the entire process is changed through or all the threads in the process will have their nice values reset to the new
process-level nice value. The new process's nice value setting overwrites the old thread's setting. Thus its possible that a thread whose
nice value had been set higher than the process-level nice value have its nice value lowered as a result of the process-level re-nicing.
RETURN VALUE
Upon successful completion, and return zero.
Otherwise, an error number is returned to indicate the error (the variable is not set).
ERRORS
If any of the following occur, the and functions return the corresponding error:
A process-scope thread was specified.
The caller does not have permission to lower the nice
value specified in nice_val.
No thread could be found corresponding to
thread.
AUTHOR
and were developed by HP.
SEE ALSO
fork(2), nice(2), setpriority(2), pthread_attr_getschedpolicy(3T), pthread_setschedparam(3T).
Pthread Library pthread_get_nice_np(3T)