We've run into something of a quandary because top doesn't recognize SAN I/O activity when reporting I/O wait.
Is there a way around this?
Does a newer version allow for this?
Top has no control over this. It simply reports the statistics gathered by the kernel. If your OS treats SAN volumes different from regular SCSI/SATA disks, that's an OS bug. What OS are you running? On linux, you can verify that this isn't a bug in top by running "vmstat 1" to print the same statistics that top prints. The "-cpu-" columns are the same ones top prints.
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.