- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Critical I/O Bottleneck
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 12:41 AM
01-07-2005 12:41 AM
Critical I/O bottleneck: CPU wait time is consistently high (93%) indicating a disk bottleneck. Check Disk Utilization and Service Time to determine which disk(s) are contributing.
My question is how do I go about this? From the bdf command, the disk(s) have plenty of free space, so what else should I look for?
Looking forward to your assistance as usual.
Thank You.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 12:49 AM
01-07-2005 12:49 AM
Re: Critical I/O Bottleneck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 12:52 AM
01-07-2005 12:52 AM
Re: Critical I/O Bottleneck
device bps sps msps
c1t2d0 0 0.0 1.0
c1t0d0 0 0.0 1.0
c2t0d0 0 0.0 1.0
c2t2d0 0 0.0 1.0
and this indicates what exactly?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 12:56 AM
01-07-2005 12:56 AM
Re: Critical I/O Bottleneck
iostat t n
where t = number of seconds to wait between snapshots, n = number of snapshots to take
e.g.
iostat 60 10
Will give you a snapshot every minute for 10 minutes.
Look at bps in particular to see which disk is busy. See man iostat for further details.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 01:06 AM
01-07-2005 01:06 AM
Re: Critical I/O Bottleneck
iostat 10
Now the monitoring program is indicating that there is no diskbottle neck any longer. It seems to be sporadic then? Is there anything else I can/should look at before leaving this issue. I have other things to look at today...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 01:10 AM
01-07-2005 01:10 AM
Re: Critical I/O Bottleneck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 01:10 AM
01-07-2005 01:10 AM
Re: Critical I/O Bottleneck
The correct command to determine if the system indeed has a serious I/O bottleneck is to use sar - specifically the syntax:
sar -d 5 10
means to collect per disk statistics every 6 seconds 10 times.
Look at avque (anything greater than 0 is bad) avwait and avserv (anything above 20 consistently is bad).
What kind of storage are you using? Do you use LVM/VxVM and do do you stripe your Oracle storage?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 01:26 AM
01-07-2005 01:26 AM
Re: Critical I/O Bottleneck
Here is the output from the command you suggested.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 01:33 AM
01-07-2005 01:33 AM
Re: Critical I/O Bottleneck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 01:33 AM
01-07-2005 01:33 AM
Re: Critical I/O Bottleneck
What is on c1t2d0? I suspect that's your culprit disk.
You may want collecting sar data over time.
mkdir /var/adm/sa
and add to root's crontab:
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/lib/sa/sa1
Over time, simply do a sar -d (to get the current day's disk sar stats) or sar -d -f /var/adm/sa/saNN (for day NN's sar stats).
If you could give use your LVM or VxVM config the better..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 01:34 AM
01-07-2005 01:34 AM
Re: Critical I/O Bottleneck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 01:44 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 01:45 AM
01-07-2005 01:45 AM
Re: Critical I/O Bottleneck
I do not see any indication of it in bdf or ioscan commands?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 01:45 AM
01-07-2005 01:45 AM
Re: Critical I/O Bottleneck
SQLDBA> MON SYSTEM IO
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 01:47 AM
01-07-2005 01:47 AM
Re: Critical I/O Bottleneck
One more thing - this is a production server and yet your OS subsystem and most other filesystems are not even mirrored. Only Oracle archive log filesystem is mirrored - I suppose your environment can take downtime since you're simply protecting Oracle archive logs?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 01:50 AM
01-07-2005 01:50 AM
Re: Critical I/O Bottleneck
Do this:
pvdisplay -v /dev/dsk/c1t2d0 2>/dev/null|grep "current"|awk '{print $3}'|awk -F\/ '{print $NF}'|sort|uniq
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 01:54 AM
01-07-2005 01:54 AM
Re: Critical I/O Bottleneck
This will match the hardware path to the device file showing you what the H/W path for c1t2d0 is, in your case 0/0/1/1.2.0 which in your document maps to VG00.
If you do pvdisplay /dev/dsk/c1t2d0
you should see /dev/vg00
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 02:08 AM
01-07-2005 02:08 AM
Re: Critical I/O Bottleneck
Assuming that I cannot get more disks or controllers. How do I go about mirroring other information such as OS information etc?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 02:14 AM
01-07-2005 02:14 AM
Re: Critical I/O Bottleneck
If this environment is realy not a big one. You can try to configure your current 4 disk environment as follows:
controller 1: c1t0d0,c1t1d0
controller 2: c2t0d0,c2t1d0
OS Disk+swap+some oracle stuff (ie. orasoftware and archive...)
VG00: - c1t0d0 + c2t0d0
Oracle Data:
VG01: c1t1d0 + c1t2d0
Or if you've deeper pockets - get a FibreChannel disk enclosuer system -- ie. DS2405.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 02:16 AM
01-07-2005 02:16 AM
Re: Critical I/O Bottleneck
In order to understand your configuration, I suppose we would need also to know the output of vgdisplay -v vg00|grep dsk and vgdisplay -v vg01|grep dsk
and also your swap usage:
swapinfo -tam
and the pvdisplay -v without the physical extents of all disks would be helpfull
All the best
Victor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 02:24 AM
01-07-2005 02:24 AM
Re: Critical I/O Bottleneck
attached is the information you required (except the last bit). I'm not sure about the command.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 02:24 AM
01-07-2005 02:24 AM
Re: Critical I/O Bottleneck
If you are unable to mirror the system disk (disk space scarce...), I would go to load oracle and other software on one disk but not connected to the same controller as the vg00 system disk, AND the 2 others each on a different controller also in vg01 AND use LVM STRIPPING for your oracle DATA...
In this way you solve your risk of contention onone disk by balancing the load through 2 controllers
All the best
Victor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 02:30 AM
01-07-2005 02:30 AM
Re: Critical I/O Bottleneck
well pv was at 0, but doesnt mind for now,
I vote:
vg00 c1t2d0
vg01 c2t2d0 for software like oracle etc NO DATA
s2vg03 c1t0d0 AND c2t0d0 # s2 for striping on 2disks...
What do you think?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 02:43 AM
01-07-2005 02:43 AM
Re: Critical I/O Bottleneck
I appreciate your help but I would have to do some serious reading up on what this would involve. Remember we do not have Online JFS. Also I am still relatively new to both Oracle and UNIX and since I was thrown in the deep end for both products, I'm still learning.
How would you go about this process if you were new?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 02:47 AM
01-07-2005 02:47 AM
Re: Critical I/O Bottleneck
Now looking more in depthat your config:
1) I would never on non RAID scsi create logical volumes of the size of lvDATA this may be one IO issue.. for performance and recovery(it can happen..) I woulnd create if not on SAN a file system greater than 30GB
once s2vg02 created with the disks c1t0d0 and c2t0d0 in it:
start creating your first stripped lv:
lvcreate -i 2 -I 64 -L 30000 -n lvol1 /dev/s2vg02
then:
newfs -F vxfs /dev/s2vg02/rlvol1
etc...
Good luck
Victor