- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- sar -d 2 6
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
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
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
02-17-2004 03:42 AM
02-17-2004 03:42 AM
c2t6d0 1.50 0.50 1 16 0.42 15.79
c2t5d0 1.50 0.50 2 32 0.57 16.48
c0t0d0 100.00 0.50 48 760 4.63 41.71
Device c0t0d0 is very busy. Is there any way to find why? What is causing that device to be so busy?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2004 03:46 AM
02-17-2004 03:46 AM
Re: sar -d 2 6
Check vgdisplay -v to see which vg the disk belongs to. This will give you some idea. vg00 can be swap vg01 ( dbase ?)
If you have installed glance/gpm you can view I/O and search for a process with havy i/o.
HTH,
Gideon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2004 04:08 AM
02-17-2004 04:08 AM
Re: sar -d 2 6
Once you check which vgs are using it fuser can also come in handy.
Paula
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2004 04:27 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2004 05:23 AM
02-17-2004 05:23 AM
Re: sar -d 2 6
avserv is 41.71 which is in milli seconds. This isn't a good number if you are looking for performance.
Try 'pvdisplay -v /dev/dsk/c0t0d0' and see the details.
If you have glance you will know more details.
What kind of disk subsystem do you have?.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2004 05:54 AM
02-17-2004 05:54 AM
Re: sar -d 2 6
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2004 05:58 AM
02-17-2004 05:58 AM
Re: sar -d 2 6
pvdisplay will show you the logical volumes in that device then you can find the corresponding mount points hence the usage.
If you don't have glance, it is tough to find what is causing the issue. However, an average service time of 41.71 is actually calculated from the disk subsystem. It's the time it took on the average for an IO request to get serviced. We would need more details.
1. How big is this disk?. How many logical volumes are there in it and what type of activity they do.
2. What is the disk subsystem?
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2004 06:00 AM
02-17-2004 06:00 AM
Re: sar -d 2 6
You'll be looking for what LVs are on this disk - i.e. is swap on the disk & it's being pounded because you've run out of memory.
And under the status cloumn that all PEs are current or free & none stale which could indicate a bad spot on the disk.
Rgds,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2004 06:03 AM
02-17-2004 06:03 AM
Re: sar -d 2 6
Pete
Pete