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)
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)
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)
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)
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)
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)
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)
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)
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> </td>". Few having more than one " " entry in it.
<tr> some td... (4 Replies)
Discussion started by: thomasraj87
4 Replies
LEARN ABOUT HPUX
gvid_no_claim_dev
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)