10 More Discussions You Might Find Interesting
1. HP-UX
First of all, forgive me if I come off as naive. Normally I'm doing day-to-day management of a Server 2008 network, so HP-UX isn't exactly my forte.
We have several HP 715/100 machines running UX 9.x, and recently one of them stopped being able to boot. In the boot menu the disk shows up with... (3 Replies)
Discussion started by: GoldnPantaloons
3 Replies
2. Solaris
Hi,
I am facing an issue with Solaris x86 machine
Machine Details:
uname -a
SunOS sol10-64 5.10 Generic_137138-09 i86pc i386 i86pc
..............................
Description:
I am trying to register a programm with proramm ID 300760 with version number 1, and tryint to create a... (0 Replies)
Discussion started by: DivakarAdari
0 Replies
3. Solaris
Hi admins,
I'm having some issues with a Solaris 10 machine. I just rebooted the box after at least 2 years running smooth and now the OS is not comming up.
This is what I see in the console (if I press Ctrl^D it loops again):
Root password for system maintenance (control-d to bypass): ... (3 Replies)
Discussion started by: verdepollo
3 Replies
4. UNIX for Dummies Questions & Answers
I know that Sun make s a version of Solaris for Sparc platforms and also an x86 (Intel/AMD) release of Solaris. Can an application that runs on Solaris/Sparc also run on a PC running the x86 release of Solaris? Would a different release be required or any re-compling of the application?
jim (1 Reply)
Discussion started by: stocksj
1 Replies
5. Solaris
OK, I have a DELL Poweredge 2850 fresh out of the box sitting here.
I'm thinking of putting Solaris 9 x86 on it.
Has anyone ever attempted this before, do you think it will work?
I dont want to get into something that is just going to be a enormus waste of time, so I am wondering if anyone... (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies
6. Solaris
Ok here goes, this MCSE is now fed up with MS, they are telling me that my Legal XP has a s/num they didnt issue.
After countless emails I am P with them and am loooking for a new OS.
Tried Linux, got it working but seems too flaky for me.
Have installed Solaris 10 X86 (on a temp pc AMD Athlon... (1 Reply)
Discussion started by: mickie
1 Replies
7. Solaris
Hi,
I have installed Solaris 8 on a PC, but I can not get the 2nd CD to install. I can log in to CDE desktop, by the way, is just black and white. I can mount the 2nd install CD, and double-click on the installer, but it does not install. Someting displays in the console and then it disappears... (1 Reply)
Discussion started by: annointed3
1 Replies
8. Solaris
hi,
need help!
i've installed solaris 9 on my x86 box...problems with kdmconfig. here what i have:
1- Dell 17" Flat monitor ( 31kHz-80kHz horizontal and 56 Hz-76Hz Vertical)
2- Matrox Millenium G550 card
what choices do i have to made?
best regards
thank you in advance (1 Reply)
Discussion started by: hmaiida
1 Replies
9. Solaris
HI All,
I have three solaris disks: disk 1 & 2 and "image" disk.
However, no instructions for installation on x86 came with them. (I downloaded from SUN.)
I've searched far and wide on the net trying to find instructions for installing Solaris on my PII 500 mhz intel machine, but have... (7 Replies)
Discussion started by: JaredsNew
7 Replies
10. UNIX for Dummies Questions & Answers
Hi There,
I search a lot across the board but didn't find answer... first of all... I installed the Companion CD. So Kde is supposed to work... I ran the script to have it in my login screen, and it's there... but when I enter it, it only kicks me to the login screen once... (1 Reply)
Discussion started by: Erythro73
1 Replies
IOSTAT(1) Linux User's Manual IOSTAT(1)
NAME
iostat - Report Central Processing Unit (CPU) statistics and input/output statistics for devices and partitions.
SYNOPSIS
iostat [ -c | -d ] [ -k ] [ -t ] [ -V ] [ -x [ device ] ] [ interval [ count ] ]
DESCRIPTION
The iostat command is used for monitoring system input/output device loading by observing the time the devices are active in relation to
their average transfer rates. The iostat command generates reports that can be used to change system configuration to better balance the
input/output load between physical disks.
The first report generated by the iostat command provides statistics concerning the time since the system was booted. Each subsequent
report covers the time since the previous report. All statistics are reported each time the iostat command is run. The report consists of a
CPU header row followed by a row of CPU statistics. On multiprocessor systems, CPU statistics are calculated system-wide as averages among
all processors. A device header row is displayed followed by a line of statistics for each device that is configured.
The interval parameter specifies the amount of time in seconds between each report. The first report contains statistics for the time since
system startup (boot). Each subsequent report contains statistics collected during the interval since the previous report. The count param-
eter can be specified in conjunction with the interval parameter. If the count parameter is specified, the value of count determines the
number of reports generated at interval seconds apart. If the interval parameter is specified without the count parameter, the iostat com-
mand generates reports continuously.
REPORTS
The iostat command generates two types of reports, the CPU Utilization report and the Device Utilization report.
CPU Utilization Report
The first report generated by the iostat command is the CPU Utilization Report. For multiprocessor systems, the CPU values are
global averages among all processors. The report has the following format:
%user
Show the percentage of CPU utilization that occurred while executing at the user level (application).
%nice
Show the percentage of CPU utilization that occurred while executing at the user level with nice priority.
%sys
Show the percentage of CPU utilization that occurred while executing at the system level (kernel).
%idle
Show the percentage of time that the CPU or CPUs were idle.
Device Utilization Report
The second report generated by the iostat command is the Device Utilization Report. The device report provides statistics on a per
physical device or partition basis. The report may show the following fields, depending on whether -x and -k options are used or
not:
Device:
This column gives the device name, which is displayed as hdiskn with 2.2 kernels, for the nth device. It is displayed as
devm-n with newer kernels, where m is the major number of the device, and n a distinctive number. When -x option is used,
the device name as listed in the /dev directory is displayed.
tps
Indicate the number of transfers per second that were issued to the device. A transfer is an I/O request to the device. Mul-
tiple logical requests can be combined into a single I/O request to the device. A transfer is of indeterminate size.
Blk_read/s
Indicate the amount of data read from the drive expressed in a number of blocks per second. Blocks are equivalent to sectors
with post 2.4 kernels and therefore have a size of 512 bytes. With older kernels, a block is of indeterminate size.
Blk_wrtn/s
Indicate the amount of data written to the drive expressed in a number of blocks per second.
Blk_read
The total number of blocks read.
Blk_wrtn
The total number of blocks written.
kB_read/s
Indicate the amount of data read from the drive expressed in kilobytes per second. Data displayed are valid only with kernels
2.4 and later.
kB_wrtn/s
Indicate the amount of data written to the drive expressed in kilobytes per second. Data displayed are valid only with ker-
nels 2.4 and later.
kB_read
The total number of kilobytes read. Data displayed are valid only with kernels 2.4 and later.
kB_wrtn
The total number of kilobytes written. Data displayed are valid only with kernels 2.4 and later.
rrqm/s
The number of read requests merged per second that were issued to the device.
wrqm/s
The number of write requests merged per second that were issued to the device.
r/s
The number of read requests that were issued to the device per second.
w/s
The number of write requests that were issued to the device per second.
rsec/s
The number of sectors read from the device per second.
wsec/s
The number of sectors written to the device per second.
rkB/s
The number of kilobytes read from the device per second.
wkB/s
The number of kilobytes written to the device per second.
avgrq-sz
The average size (in sectors) of the requests that were issued to the device.
avgqu-sz
The average queue length of the requests that were issued to the device.
await
The average time (in milliseconds) for I/O requests issued to the device to be served.
svctm
The average service time (in milliseconds) for I/O requests that were issued to the device.
%util
Percentage of CPU time during which I/O requests were issued to the device.
OPTIONS
-c The -c option is exclusive of the -d option and displays only the cpu usage report.
-d The -d option is exclusive of the -c option and displays only the device utilization report.
-k Display statistics in kilobytes per second instead of blocks per second. Data displayed are valid only with kernels 2.4 and later.
-t Print the time for each report displayed.
-V Print version number and usage then exit.
-x device
Display extended statistics. If no device is given on the command line, then extended statistics are displayed for every device reg-
istered in the /proc/partitions file. Please note that Linux kernel needs to be patched for this option to work.
ENVIRONMENT
The iostat command takes into account the following environment variable:
S_TIME_FORMAT
If this variable exists and its value is ISO then the current locale will be ignored when printing the date in the report header.
The iostat command will use the ISO format (YYYY-MM-DD) instead.
EXAMPLES
iostat
Display a single history since boot report for all CPU and Devices.
iostat -d 2
Display a continuous device report at two second intervals.
iostat -d 2 6
Display six reports at two second intervals for all devices.
BUGS
/proc filesystem must be mounted for iostat to work.
FILE
/proc/stat contains system statisitics.
/proc/partitions contains statistics for the devices.
AUTHOR
Sebastien Godard <sebastien.godard@wanadoo.fr>
SEE ALSO
vmstat(8), sar(1), mpstat(1)
http://perso.wanadoo.fr/sebastien.godard/
Linux JANUARY 2002 IOSTAT(1)
