Sponsored Content
Operating Systems Solaris Understanding an iostat entry Post 302762453 by shoto2007 on Monday 28th of January 2013 12:58:36 PM
Old 01-28-2013
Understanding an iostat entry

Hi all,
I'm working on a solaris server.
there are no any hardware issue.
but I get the following isostat output:

Code:
# iostat -en
  ---- errors --- 
  s/w h/w trn tot device
    0   0   0   0 c0t5000CCA012AB0081d0
    0   0   0   0 c0t5000CCA012B4CC61d0
    0   0   0   0 c0t5000CCA012A4AA61d0
    0   0   0   0 c0t5000CCA012AAACF5d0
    0   0   0   0 c0t5000CCA012A4E489d0
    0   0   0   0 c0t5000CCA012AD3E69d0
    0   0   0   0 c0t5000CCA012B4B5C9d0
    0   0   0   0 c0t5000CCA012A81FADd0
    0  12   0  12 c1t0d0
    0  12   0  12 c5t0d0
    0   1   0   1 rmt/0
    0   0   0   0 Sdp031:vold(pid679)

I though that I had 2 faulty devices, but in iostat -En, these devices are Virtual.

Code:
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
Illegal Request: 0 Predictive Failure Analysis: 0 
c0t5000CCA012A81FADd0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
Vendor: HITACHI  Product: H106030SDSUN300G Revision: A2B0 Device Id: id1,sd@n5000cca012a81fac 
Size: 300.00GB <299999999488 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
Illegal Request: 0 Predictive Failure Analysis: 0 
c1t0d0           Soft Errors: 0 Hard Errors: 12 Transport Errors: 0 
Vendor: AMI      Product: Virtual Floppy   Revision: 1.00 Device Id: 
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 12 Recoverable: 0 
Illegal Request: 6 Predictive Failure Analysis: 0 
c5t0d0           Soft Errors: 0 Hard Errors: 12 Transport Errors: 0 
Vendor: AMI      Product: Virtual CDROM    Revision: 1.00 Device Id: 
Size: 0.00GB <0 bytes>

I dont't understand these entries and need to know if it is possible to remove these entries from iostat.

Thx
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

iostat output what is that mean

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

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... (3 Replies)
Discussion started by: dj_is
3 Replies

3. AIX

how to identified this iostat value

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. Solaris

iostat -Eni

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

5. Red Hat

iostat on Redhat 5

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. Shell Programming and Scripting

IOSTAT monitoring

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

7. Solaris

How to use IOSTAT command

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

8. AIX

Help with iostat

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

9. How to Post in the The UNIX and Linux Forums

Help me, write a bash script to delete parent entry with all their child entry in LDAP UNIX server

Hi All, Please help me and guide me to write a bash/shell script on Linux box to delete parent entry with all their child entries. example: Parent is : ---------- dn: email=yogesh.kumar@wipro.com, o=wipro, o=in child is: ---------- dn: cn: yogesh kumar, email=yogesh.kumar@wipro.com,... (1 Reply)
Discussion started by: Chand
1 Replies

10. Shell Programming and Scripting

How to replace multiple "&nbsp;" entry with in <td> tag into single entry using sed?

I have the input file like this. Input file: 12.txt 1) There are one or more than one <tr> tags in same line. 2) Some tr tags may have one <td> or more tna one <td> tags within it. 3) Few <td> tags having "<td> &nbsp; </td>". Few having more than one "&nbsp;" entry in it. <tr> some td... (4 Replies)
Discussion started by: thomasraj87
4 Replies
gvid_no_claim_dev(5)						File Formats Manual					      gvid_no_claim_dev(5)

NAME
gvid_no_claim_dev - PCI Vendor/Device ID that the gvid graphics driver will not claim VALUES
Failsafe Default Allowed values Recommended values Specific to the device you wish to prevent from claiming. DESCRIPTION
This tunable specifies the PCI Vendor ID and/or Device ID of a graphics device that the HP graphics driver should not claim. The graphics driver was designed to be a general purpose driver for all PCI graphics cards. As a result, the driver will attempt to claim any PCI graphics display device found on the system. This can be a problem for graphics device developers who need their own graphics driver to claim their own graphics device. The value of will specify a PCI Vendor ID and/or Device ID of a graphics card that the gvid graphics driver should not claim. It is a 32 bit number, with the upper 16 bits containing the PCI Vendor ID and the lower 16 bits containing the PCI Device ID. Either the Vendor ID or Device ID can use a wildcard value of For example, if is set to the value the driver will ignore graphics devices with a PCI Vendor ID of and a Device ID of If is set to the driver will not claim any graphics cards with a Vendor ID of regardless of the Device ID. Who Is Expected to Change This Tunable? Anyone who wishes the graphics driver to ignore a specific graphics device. This will typically be someone writing their own graphics driver for their own hardware. Restrictions on Changing Changes to this tunable take effect at the next reboot. What Other Tunables Should Be Changed at the Same Time? None. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. Tunable Kernel Parameters gvid_no_claim_dev(5)
All times are GMT -4. The time now is 12:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy