08-09-2007
Help with iostat ...
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 temporary file are held, but I am not sure how to check to make sure.
So, how can I see what directories are on this device (oh, and I do not have root access).
Can anyone offer any tips/tricks for tuning in this situation?
Thank you very much for any help.
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. 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
3. 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
4. Shell Programming and Scripting
Friends.
I have to compare iostat -x output with a tool on solaris. Now there is column called wait in the output field which is showing zero. Now, in order to create some load on my system this is what i am doing
I am creating a file using dd command , the size of which is... (5 Replies)
Discussion started by: achak01
5 Replies
5. 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
6. 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
7. UNIX for Dummies Questions & Answers
Hi Unix experts,
I have a question regarding a disk failure seen in "iostat -Enm" output:
# iostat -Enm
c1t0d0 Soft Errors: 0 Hard Errors: 7 Transport Errors: 9
Vendor: FUJITSU Product: MAU3073NCSUN72G Revision: 0802 Serial No: 0514F005M0
Size: 73.40GB <73400057856 bytes>
Media... (5 Replies)
Discussion started by: dyavuzy1
5 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 SUSE
smp_rep_phy_err_log
SMP_REP_PHY_ERR_LOG(8) SMP_UTILS SMP_REP_PHY_ERR_LOG(8)
NAME
smp_rep_phy_err_log - invoke REPORT PHY ERROR LOG SMP function
SYNOPSIS
smp_rep_phy_err_log [--help] [--hex] [--interface=PARAMS] [--phy=ID] [--raw] [--sa=SAS_ADDR] [--verbose] [--version] SMP_DEVICE[,N]
DESCRIPTION
Sends a SAS Management Protocol (SMP) REPORT PHY ERROR LOG request function to a SMP target. The SMP target is identified by the SMP_DEVICE
and the SAS_ADDR. Depending on the interface, the SAS_ADDR may be deduced from the SMP_DEVICE. With one interface there is one SMP_DEVICE
per machine so the SMP_DEVICE,N syntax is needed to differentiate between HBAs if there are multiple present.
OPTIONS
Mandatory arguments to long options are mandatory for short options as well.
-h, --help
output the usage message then exit.
-H, --hex
output the response in hexadecimal.
-I, --interface=PARAMS
interface specific parameters. In this case "interface" refers to the path through the operating system to the SMP initiator. See
the smp_utils man page for more information.
-p, --phy=ID
phy identifier. ID is a value between 0 and 127. Default is 0.
-r, --raw
send the response to stdout in binary. All error messages are sent to stderr.
-s, --sa=SAS_ADDR
specifies the SAS address of the SMP target device. Typically this is an expander. This option may not be needed if the SMP_DEVICE
has the target's SAS address within it. The SAS_ADDR is in decimal but most SAS addresses are shown in hexadecimal. To give a number
in hexadecimal either prefix it with '0x' or put a trailing 'h' on it.
-v, --verbose
increase the verbosity of the output. Can be used multiple times
-V, --version
print the version string and then exit.
NOTES
Similar information is maintained for SAS SSP target phys (e.g. on a SAS disk). It can be obtained from the Protocol Specific Port log page
with the sg_logs utility.
Similar information may be obtained for SAS initiator phys (e.g. on a SAS HBA). As an example in Linux 2.6.28 error information can be
found in this directory /sys/class/sas_phy/phy-4:0 (for the phy 0 in SCSI/SAS host 4).
Similar information may be obtained for SATA device phys (e.g. on a SATA disk). If there is a SAT layer between OS and the SATA device then
the sg_sat_phy_event utility can fetch the information.
CONFORMING TO
The SMP REPORT PHY ERROR LOG function was introduced in SAS-1 . The "Expander change count" field was added in SAS-2 .
AUTHORS
Written by Douglas Gilbert.
REPORTING BUGS
Report bugs to <dgilbert at interlog dot com>.
COPYRIGHT
Copyright (C) 2006-2008 Douglas Gilbert
This software is distributed under a FreeBSD license. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR-
POSE.
SEE ALSO
smp_utils, smp_phy_control(smp_utils), sg_logs(sg3_utils), sg_sat_phy_event(sg3_utils)
smp_utils-0.94 December 2008 SMP_REP_PHY_ERR_LOG(8)