Upgraded: snmpdiskio 0.9.6 (Disk I/O statistics on Linux)

Templates, scripts for templates, scripts and requests for templates.

Moderators: Developers, Moderators

Post Reply
User avatar
gandalf
Developer
Posts: 22383
Joined: Thu Dec 02, 2004 2:46 am
Location: Muenster, Germany
Contact:

Post by gandalf »

There seems to be an error with the XML file, as no OID that should be queried for the index is shown
Reinhard
plouj
Posts: 7
Joined: Thu Aug 31, 2006 6:04 pm

I'm stuck at the end of installation

Post by plouj »

I am stuck at step 3. "USAGE" of the installation process.
After adding the "Disk - I/O (bytes/sec)" graph template to my host template, I still cannot add this same template to an already existing device. I just don't see the option in the "Add Graph Template:" drop down menu.

I even added the appropriate data queries to my device already, but still cannot see the option for adding a graph. I would like to figure out how to add the graph through the device editing page rather than adding a 'disconnected' graph to the tree and then associating it with the device later. As far as I know, all the previous installation steps were completed successfully, especially the template XML file importation.
plouj
Posts: 7
Joined: Thu Aug 31, 2006 6:04 pm

Post by plouj »

Well, it looks like I don't actually need to add the Graph Template to my existing host. My device I/O is being monitored and graphed just fine now.
driden91
Cacti User
Posts: 52
Joined: Fri Jan 20, 2006 10:38 am

Post by driden91 »

I have the same problem .
i follow the README instruction to setup it.
And that's the debug mode of the graph management

Code: Select all

[ RRDTool Command:

/usr/bin/rrdtool graph - \
--imgformat=PNG \
--start=-108000 \
--end=-300 \
--title="poste_perso-2 - Disk I/O (bytes/sec) - sda1" \
--rigid \
--base=1000 \
--height=120 \
--width=500 \
--alt-autoscale-max \
--lower-limit=0 \
--vertical-label="bytes per second" \
--slope-mode \
DEF:a="/home/www/cacti/rra/poste_perso2_io_read_164.rrd":io_read:AVERAGE \
DEF:b="/home/www/cacti/rra/poste_perso2_io_read_164.rrd":io_write:AVERAGE \
AREA:a#4668E4:"Read"  \
GPRINT:a:AVERAGE:" Average\:%8.2lf %s"  \
GPRINT:a:MIN:"Min\:%8.2lf %s"  \
GPRINT:a:MAX:"Max\:%8.2lf %s"  \
GPRINT:a:LAST:"Current\:%8.2lf %s\n"  \
AREA:b#EAAF00:"Write":STACK \
GPRINT:b:AVERAGE:"Average\:%8.2lf %s"  \
GPRINT:b:MIN:"Min\:%8.2lf %s"  \
GPRINT:b:MAX:"Max\:%8.2lf %s"  \
GPRINT:b:LAST:"Current\:%8.2lf %s\n" 

RRDTool Says:

ERROR: opening '/home/www/cacti/rra/poste_perso2_io_read_164.rrd': No such file or directory
/code]


what is the solution please ?
cspenpen
Cacti User
Posts: 67
Joined: Tue Dec 05, 2006 5:10 am

php problem

Post by cspenpen »

Hi

when I select the partitions you want graphs created for and click Create.

then show this error messages
Notice: Undefined index: sgg_13 in /var/www/html/cacti/graphs_new.php on line 71

Notice: Undefined index: sgg_13 in /var/www/html/cacti/graphs_new.php on line 71

Notice: Undefined index: sgg_13 in /var/www/html/cacti/graphs_new.php on line 71

Notice: Undefined index: sgg_13 in /var/www/html/cacti/graphs_new.php on line 71

Notice: Undefined index: sgg_13 in /var/www/html/cacti/graphs_new.php on line 71

Notice: Undefined index: sgg_13 in /var/www/html/cacti/graphs_new.php on line 71

Notice: Undefined index: sgg_13 in /var/www/html/cacti/graphs_new.php on line 71

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/cacti/graphs_new.php:71) in /var/www/html/cacti/graphs_new.php on line 322
OS : centOS3
PHP:php-imap-4.3.2-26.ent php-4.3.2-26.ent php-mysql-4.3.2-26.ent php-ldap-4.3.2-26.ent

HTTPD:httpd-2.0.46-56.ent.centos.2

snmp:net-snmp-libs-5.0.9-2.30E.19 net-snmp-utils-5.0.9-2.30E.19 net-snmp-5.0.9-2.30E.19 net-snmp-devel-5.0.9-2.30E.19

mysql:mysql-devel-3.23.58-16.RHEL3.1 mysql-3.23.58-16.RHEL3.1 php-mysql-4.3.2-26.ent libdbi-dbd-mysql-0.6.5-5 mysql-server-3.23.58-16.RHEL3.1


help me & thx a lot !!
User avatar
gandalf
Developer
Posts: 22383
Joined: Thu Dec 02, 2004 2:46 am
Location: Muenster, Germany
Contact:

Post by gandalf »

driden91 wrote:I have the same problem .
i follow the README instruction to setup it.
And that's the debug mode of the graph management

Code: Select all

[ RRDTool Command:

/usr/bin/rrdtool graph - \
--imgformat=PNG \
--start=-108000 \
--end=-300 \
--title="poste_perso-2 - Disk I/O (bytes/sec) - sda1" \
--rigid \
--base=1000 \
--height=120 \
--width=500 \
--alt-autoscale-max \
--lower-limit=0 \
--vertical-label="bytes per second" \
--slope-mode \
DEF:a="/home/www/cacti/rra/poste_perso2_io_read_164.rrd":io_read:AVERAGE \
DEF:b="/home/www/cacti/rra/poste_perso2_io_read_164.rrd":io_write:AVERAGE \
AREA:a#4668E4:"Read"  \
GPRINT:a:AVERAGE:" Average\:%8.2lf %s"  \
GPRINT:a:MIN:"Min\:%8.2lf %s"  \
GPRINT:a:MAX:"Max\:%8.2lf %s"  \
GPRINT:a:LAST:"Current\:%8.2lf %s\n"  \
AREA:b#EAAF00:"Write":STACK \
GPRINT:b:AVERAGE:"Average\:%8.2lf %s"  \
GPRINT:b:MIN:"Min\:%8.2lf %s"  \
GPRINT:b:MAX:"Max\:%8.2lf %s"  \
GPRINT:b:LAST:"Current\:%8.2lf %s\n" 

RRDTool Says:

ERROR: opening '/home/www/cacti/rra/poste_perso2_io_read_164.rrd': No such file or directory
/code]


what is the solution please ?[/quote]This debug does not hekp here. It is shown, that the rrd file does not exist. There are lots of possible reasons for that
- wrong permissions on /rra 
- host reported as "down" or "unknown" in the devices list: cacti does not see it
- many more
Have a look at my "NaN Debugging" howto. Perform it step by step and report your results, again step by step
Reinhard
case_h99
Posts: 6
Joined: Sat Nov 25, 2006 3:57 pm

read or write?

Post by case_h99 »

I use Centos 4.4 (kernel 2.6)

I sucessfully installed the last version of the script and the template

I monitor a server whit no much traffic... btw I think only syslog is using disk.
In fact if I use iostat, I can see this:

Code: Select all

Device:            tps   Blk_read/s   Blk_wrtn/s   Blk_read   Blk_wrtn
hda2            131.68         0.00      1053.47          0       1064
And in /proc/diskstats I can see at time n

Code: Select all

3    2 hda2 15533 469438 10373941 82991528
and at time n+1

Code: Select all

3    2 hda2 15533 469438 10386042 83088336
What I mean is: there are only writtens but...
whit your script I get increments on hdOutBlocks

hdOutBlocks are displayed as reads in the graph


Well... where is the problem? I'm not understanding something?
hdInBlocks or hdOutBlocks: who really represents the writes?

Thanks.
User avatar
gandalf
Developer
Posts: 22383
Joined: Thu Dec 02, 2004 2:46 am
Location: Muenster, Germany
Contact:

Post by gandalf »

Sorry, it is not _my_ script. So I can't answer your question as I do not use it on my own
Reinhard
mavericque
Posts: 1
Joined: Sat Jan 13, 2007 7:36 am

Problem get snmpdiskio working net-snmp 5.4 kernel 2.6.18.2

Post by mavericque »

Hi all,
snmpdiskio is a great extension to cacti! I have used it on a couple of systems. But I can't get it to work on net-snmp 5.4 and kernel 2.6.18.2. I figured out that the exec clause is deprecated, so I use the extend clause in snmpd.conf:

Code: Select all

extend .1.3.6.1.4.1.2021.54 hdNum /usr/local/bin/snmpdiskio hdNum
extend .1.3.6.1.4.1.2021.55 hdIndex /usr/local/bin/snmpdiskio hdIndex
extend .1.3.6.1.4.1.2021.56 hdDescr /usr/local/bin/snmpdiskio hdDescr
extend .1.3.6.1.4.1.2021.57 hdInBlocks /usr/local/bin/snmpdiskio hdInBlocks
extend .1.3.6.1.4.1.2021.58 hdOutBlocks /usr/local/bin/snmpdiskio hdOutBlocks
The problem is, that running

Code: Select all

snmpwalk -v 1 -c public localhost .1.3.6.1.4.1.2021.55.101
returns nothing. When I do

Code: Select all

snmpwalk -v 1 -c public localhost .1.3.6.1.4.1.2021.55
the following output is generated:

Code: Select all

UCD-SNMP-MIB::ucdavis.55.1.0 = INTEGER: 1
UCD-SNMP-MIB::ucdavis.55.2.1.2.7.104.100.73.110.100.101.120 = STRING: "/usr/local/bin/snmpdiskio"
UCD-SNMP-MIB::ucdavis.55.2.1.3.7.104.100.73.110.100.101.120 = STRING: "hdIndex"
UCD-SNMP-MIB::ucdavis.55.2.1.4.7.104.100.73.110.100.101.120 = ""
UCD-SNMP-MIB::ucdavis.55.2.1.5.7.104.100.73.110.100.101.120 = INTEGER: 5
UCD-SNMP-MIB::ucdavis.55.2.1.6.7.104.100.73.110.100.101.120 = INTEGER: 1
UCD-SNMP-MIB::ucdavis.55.2.1.7.7.104.100.73.110.100.101.120 = INTEGER: 1
UCD-SNMP-MIB::ucdavis.55.2.1.20.7.104.100.73.110.100.101.120 = INTEGER: 4
UCD-SNMP-MIB::ucdavis.55.2.1.21.7.104.100.73.110.100.101.120 = INTEGER: 1
UCD-SNMP-MIB::ucdavis.55.3.1.1.7.104.100.73.110.100.101.120 = STRING: "1"
UCD-SNMP-MIB::ucdavis.55.3.1.2.7.104.100.73.110.100.101.120 = STRING: "1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30"
UCD-SNMP-MIB::ucdavis.55.3.1.3.7.104.100.73.110.100.101.120 = INTEGER: 30
UCD-SNMP-MIB::ucdavis.55.3.1.4.7.104.100.73.110.100.101.120 = INTEGER: 0
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.1 = STRING: "1"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.2 = STRING: "2"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.3 = STRING: "3"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.4 = STRING: "4"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.5 = STRING: "5"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.6 = STRING: "6"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.7 = STRING: "7"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.8 = STRING: "8"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.9 = STRING: "9"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.10 = STRING: "10"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.11 = STRING: "11"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.12 = STRING: "12"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.13 = STRING: "13"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.14 = STRING: "14"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.15 = STRING: "15"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.16 = STRING: "16"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.17 = STRING: "17"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.18 = STRING: "18"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.19 = STRING: "19"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.20 = STRING: "20"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.21 = STRING: "21"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.22 = STRING: "22"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.23 = STRING: "23"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.24 = STRING: "24"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.25 = STRING: "25"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.26 = STRING: "26"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.27 = STRING: "27"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.28 = STRING: "28"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.29 = STRING: "29"
UCD-SNMP-MIB::ucdavis.55.4.1.2.7.104.100.73.110.100.101.120.30 = STRING: "30"

Whereas on a system where snmpdiskio works fine with cacti (kernel 2.6.13, net-snmp 5.2.1, using exec in sbmpd.conf), the output of the same command is:

Code: Select all

pc:~> snmpwalk -v 1 -c public localhost .1.3.6.1.4.1.2021.55
UCD-SNMP-MIB::ucdavis.55.1.1 = INTEGER: 1
UCD-SNMP-MIB::ucdavis.55.2.1 = STRING: "hdIndex"
UCD-SNMP-MIB::ucdavis.55.3.1 = STRING: "/usr/local/bin/snmpdiskio hdIndex"
UCD-SNMP-MIB::ucdavis.55.100.1 = INTEGER: 0
UCD-SNMP-MIB::ucdavis.55.101.1 = STRING: "1"
UCD-SNMP-MIB::ucdavis.55.101.2 = STRING: "2"
UCD-SNMP-MIB::ucdavis.55.101.3 = STRING: "3"
UCD-SNMP-MIB::ucdavis.55.101.4 = STRING: "4"
UCD-SNMP-MIB::ucdavis.55.101.5 = STRING: "5"
UCD-SNMP-MIB::ucdavis.55.101.6 = STRING: "6"
UCD-SNMP-MIB::ucdavis.55.101.7 = STRING: "7"
UCD-SNMP-MIB::ucdavis.55.101.8 = STRING: "8"
UCD-SNMP-MIB::ucdavis.55.101.9 = STRING: "9"
UCD-SNMP-MIB::ucdavis.55.101.10 = STRING: "10"
UCD-SNMP-MIB::ucdavis.55.101.11 = STRING: "11"
UCD-SNMP-MIB::ucdavis.55.101.12 = STRING: "12"
UCD-SNMP-MIB::ucdavis.55.101.13 = STRING: "13"
UCD-SNMP-MIB::ucdavis.55.101.14 = STRING: "14"
UCD-SNMP-MIB::ucdavis.55.101.15 = STRING: "15"
UCD-SNMP-MIB::ucdavis.55.101.16 = STRING: "16"
UCD-SNMP-MIB::ucdavis.55.101.17 = STRING: "17"
UCD-SNMP-MIB::ucdavis.55.101.18 = STRING: "18"
UCD-SNMP-MIB::ucdavis.55.101.19 = STRING: "19"
UCD-SNMP-MIB::ucdavis.55.101.20 = STRING: "20"
UCD-SNMP-MIB::ucdavis.55.101.21 = STRING: "21"
UCD-SNMP-MIB::ucdavis.55.101.22 = STRING: "22"
UCD-SNMP-MIB::ucdavis.55.101.23 = STRING: "23"
UCD-SNMP-MIB::ucdavis.55.101.24 = STRING: "24"
UCD-SNMP-MIB::ucdavis.55.101.25 = STRING: "25"
UCD-SNMP-MIB::ucdavis.55.101.26 = STRING: "26"
UCD-SNMP-MIB::ucdavis.55.101.27 = STRING: "27"
UCD-SNMP-MIB::ucdavis.55.101.28 = STRING: "28"
UCD-SNMP-MIB::ucdavis.55.101.29 = STRING: "29"
UCD-SNMP-MIB::ucdavis.55.101.30 = STRING: "30"
UCD-SNMP-MIB::ucdavis.55.101.31 = STRING: "31"
UCD-SNMP-MIB::ucdavis.55.101.32 = STRING: "32"
UCD-SNMP-MIB::ucdavis.55.101.33 = STRING: "33"
UCD-SNMP-MIB::ucdavis.55.101.34 = STRING: "34"
UCD-SNMP-MIB::ucdavis.55.102.1 = INTEGER: 0
UCD-SNMP-MIB::ucdavis.55.103.1 = ""

So, the data is being returned under different OIDs. Can anyone help me on how to get this working on the new system?
Do I have to modify the file resource/snmp_queries/partition.xml?

Thanks in advance
jeffreymlewis
Posts: 1
Joined: Wed Jan 24, 2007 6:51 pm

snmpdiskio reports wrong numbers on RHEL 3

Post by jeffreymlewis »

First I'd like to say thanks so much for posting your scripts and graph templates. They are most useful!

A few weeks ago I discovered that the I/O stats I'm graphing are not accurate. I think I've discovered the problem.

The 'snmpdiskio' script seems to be grabbing the wrong fields on Redhat 3. The 'hdInBlocks' function is grabbing $10 which is the 'wmerge' field according to the header in /proc/partitions. The 'hdOutBlocks' function is grabbing $8 which is 'ruse' on Redhat 3.

Code: Select all

function hdInBlocks()
{
        awk ' $1 ~ /[0-9]+/ && $2 ~ /[0-9]+/ && $10 ~ /[0-9]+/ { printf "%.0f\n", $10 * 512 }
              $1 ~ /[0-9]+/ && $2 ~ /[0-9]+/ && $10 !~ /[0-9]+/ { printf "%.0f\n", $5 * 512 } ' $PROCFILE
}

function hdOutBlocks()
{
        awk ' $1 ~ /[0-9]+/ && $2 ~ /[0-9]+/ && $8 ~ /[0-9]+/ { printf "%.0f\n", $8 * 512 }
              $1 ~ /[0-9]+/ && $2 ~ /[0-9]+/ && $8 !~ /[0-9]+/ { printf "%.0f\n", $7 * 512 } ' $PROCFILE
}
I think we should be grabbing the 'wsect' and 'rsect' fields instead, which are $11 and $7 respectively.

Code: Select all

# head -1 /proc/partitions
major minor  #blocks  name     rio rmerge rsect ruse wio wmerge wsect wuse running use aveq
Can anyone confirm my suspicion? I've modified the 'snmpdiskio' script on a few of my systems and it now seems to be graphing accurate numbers.

Thanks,
Jeff
mmuse
Posts: 8
Joined: Fri Jan 26, 2007 6:43 pm

trouble creating graph from 'ucd/net - Device I/O - R/W'

Post by mmuse »

The "Custom Data [Template: ucd/net - Device I/O]" is asking for the following info:
Index Type
Index Value
Output Type ID

What should I enter for each?
jspilon
Posts: 19
Joined: Wed Jan 17, 2007 6:53 pm
Location: Montreal, QC

Post by jspilon »

has anyone manage to get the Data query to resolve partitions to mount points ?
jspilon
Posts: 19
Joined: Wed Jan 17, 2007 6:53 pm
Location: Montreal, QC

Post by jspilon »

Hello,

First off, thanks for this template. I am planning to aggregate all my partitions' data into one graph, but I see that the drive has less i/o than all the partitions added together... (sum of sda* = sda isn't true) any idea why ???
ravton
Posts: 3
Joined: Mon Jan 19, 2004 6:24 pm

Patch for CentOS (and probably others)

Post by ravton »

The patch below gets this to work on CentOS, Redhat and likely other 2.6 kernels. Fixed is wrong fields. Tested with RAID, LVM, and partitions - the data all lines up correctly now amongst all them!

Enjoy and thanks to the original author!


38c38
< $1 ~ /[0-9]+/ && $2 ~ /[0-9]+/ && $10 !~ /[0-9]+/ { printf "%.0f\n", $7 * 512 } ' $PROCFILE
---
> $1 ~ /[0-9]+/ && $2 ~ /[0-9]+/ && $10 !~ /[0-9]+/ { printf "%.0f\n", $5 * 512 } ' $PROCFILE
43,44c43,44
< awk ' $1 ~ /[0-9]+/ && $2 ~ /[0-9]+/ && $8 ~ /[0-9]+/ { printf "%.0f\n", $6 * 512 }
< $1 ~ /[0-9]+/ && $2 ~ /[0-9]+/ && $8 !~ /[0-9]+/ { printf "%.0f\n", $5 * 512 } ' $PROCFILE
---
> awk ' $1 ~ /[0-9]+/ && $2 ~ /[0-9]+/ && $8 ~ /[0-9]+/ { printf "%.0f\n", $8 * 512 }
> $1 ~ /[0-9]+/ && $2 ~ /[0-9]+/ && $8 !~ /[0-9]+/ { printf "%.0f\n", $7 * 512 } ' $PROCFILE
pdestefanis
Posts: 9
Joined: Tue Dec 19, 2006 11:39 am

Post by pdestefanis »

This makes sense. According to what I've found for 2.6 kernels in http://developer.osdl.org/dev/robustmut ... ostats.txt, the fields from /proc/diskstats are fixed by the patch in the previous post.

For partitions:

Field 1 -- # of reads issued
This is the total number of reads issued to this partition.
Field 2 -- # of sectors read
This is the total number of sectors requested to be read from this
partition.
Field 3 -- # of writes issued
This is the total number of writes issued to this partition.
Field 4 -- # of sectors written
This is the total number of sectors requested to be written to
this partition.

For drives:

Field 1 -- # of reads issued
This is the total number of reads completed successfully.
Field 2 -- # of reads merged, field 6 -- # of writes merged
Reads and writes which are adjacent to each other may be merged for
efficiency. Thus two 4K reads may become one 8K read before it is
ultimately handed to the disk, and so it will be counted (and queued)
as only one I/O. This field lets you know how often this was done.
Field 3 -- # of sectors read
This is the total number of sectors read successfully.
Field 4 -- # of milliseconds spent reading
This is the total number of milliseconds spent by all reads (as
measured from __make_request() to end_that_request_last()).
Field 5 -- # of writes completed
This is the total number of writes completed successfully.
Field 7 -- # of sectors written
This is the total number of sectors written successfully.
Field 8 -- # of milliseconds spent writing
This is the total number of milliseconds spent by all writes (as
measured from __make_request() to end_that_request_last()).
Field 9 -- # of I/Os currently in progress
The only field that should go to zero. Incremented as requests are
given to appropriate request_queue_t and decremented as they finish.
Field 10 -- # of milliseconds spent doing I/Os
This field is increases so long as field 9 is nonzero.
Field 11 -- weighted # of milliseconds spent doing I/Os
This field is incremented at each I/O start, I/O completion, I/O
merge, or read of these stats by the number of I/Os in progress
(field 9) times the number of milliseconds spent doing I/O since the
last update of this field. This can provide an easy measure of both
I/O completion time and the backlog that may be accumulating.

The only thing I don't like is the fixed sector size (512), but I can't find a place where the sector size is specified. I know, it's fairly standard anyway.

Cheers,

Pablo
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest