cancel
Showing results for 
Search instead for 
Did you mean: 

Help with sar

SOLVED
Go to solution
KPS
Super Advisor

Help with sar

We're looking at some SAR performance data that we have collected. We've gzipped the sar data file and have copied that file to another HP-UX system where we have unzipped it for analysis.

I'm trying to use "sar -d -f " to look at disk i/o stats.

I'm curious to why the disk devices are showing up as hex numbers

09:00:10 c0t6d0 41.62 0.50 111 1028 0.00 5.35
c2t6d0 26.88 0.50 104 1001 0.00 3.50
0x1f/0x1b0100 7.52 0.50 77 1401 0.00 7.85
0x1f/0x1e0100 6.62 0.50 75 1379 0.00 8.74
0x1f/0x1d0100 6.42 0.50 75 1366 0.00 8.43
0x1f/0x1b0200 7.92 0.50 16 461 0.00 5.91
0x1f/0x1e0200 5.02 0.50 14 449 0.00 4.67
0x1f/0x1d0200 7.32 0.50 13 441 0.00 6.27
0x1f/0x1b0300 2.91 0.50 6 120 0.00 4.62
0x1f/0x1e0300 3.51 0.50 6 124 0.00 5.86
0x1f/0x1d0300 3.11 0.50 7 130 0.00 4.59
0x1f/0x1b0400 29.69 0.50 82 1780 0.00 4.49
0x1f/0x1e0400 30.79 0.50 79 1696 0.00 4.64
0x1f/0x1d0400 29.89 0.50 80 1740 0.00 4.37
0x1f/0x1b0500 11.33 0.50 20 318 0.00 7.72
0x1f/0x1e0500 10.43 0.50 19 300 0.00 6.91
0x1f/0x1d0500 11.33 0.50 20 326 0.00 7.63
0x1f/0x1b0600 4.31 0.50 11 181 0.00 10.00
0x1f/0x1e0600 5.62 0.50 12 205 0.00 9.99


We're not sure why the output is showing up like this. I was expecting to see the disk devices in /dev/dsk/c#t#d# format...

I'm wondering what would have caused this and if someone could help me figure out if there's a way to change this?

Thanks,
/KPS

2 REPLIES
Duncan Edmonstone
Honored Contributor
Solution

Re: Help with sar

I wonder if the disks on your SAN (I'm guessing you have one...) have been renumbered since the data was gathered... do you see the same thing if you look at sar data right now (sar -d 1 1) ? I'd be surprised if sar is intelligent enough to figure out how paths have changed.

HTH

Duncan

HTH

Duncan
KPS
Super Advisor

Re: Help with sar

Duncan,

I never knew that if we move the sar data file to another system, that these results could exist. You were right we have SAN attached storage and that was what I was really trying to look at sar statistics for. So since that storage wasn't visible to the system we moved the sar data to, this was causing this behavior. I moved it back to the original server (the source) where we had captured the sar collection and all was back to normal.

Thanks so much!!

/KPS