SUMMARY: iostat -E RPM reporting

From: Deb Heller-Evans <deb_at_tickleme.llnl.gov>
Date: Thu Feb 07 2002 - 11:13:02 EST
The consensus was that the "sd" driver cannot always get the correct
RPM value.  Casper Dik related, "The specific kstat was removed and 
later releases do not report "RPM"."

And he pointed out that since they're ST318406, they are rated to run
at 10000 RPM.  Makes sense to me!

Thanks also to Mark McManus.

d

======================================================================

Original Post:

Scott Pham's summary mentioned "iostat -E" and it reminded me of  
questions I have about how this command gets its information.

For example, iostat -E reports the following on one of our 5.6 servers:

sd45    Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
Vendor: SEAGATE  Product: ST318404LSUN18G  Revision: 8507 Serial No: 0024T0JLF9 
RPM: 7200 Heads: 19 Size: 18.11GB <18110967808 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
Illegal Request: 0 Predictive Failure Analysis: 0 

However, the disk is supposed to be rated 10000 RPM, not 7200.  So, it
brings to mind a couple of questions I don't know how to answer:

1.  Is there a limitation in the 5.6 OS that won't report RPM > 7200?

2.  Are the disks mis-labeled?

3.  How can I determine if the disks really are or aren't rated at what
    we believe we purchased, ie. 10000 RPM (all other data is correct in
        the output of iostat -E)?


"If it dies, it's biology.  If it blows up, it's chemistry,
and if it doesn't work, it's physics."
                                        -- University bathroom graffito
t?t
 ~ 
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
Received on Thu Feb 7 10:14:12 2002

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:42:33 EST