Brian Behlendorf a69052be7f Initial zio delay timing ... While there is no right maximum timeout for a disk IO we can start laying the ground work to measure how long they do take in practice. This change simply measures the IO time and if it exceeds 30s an event is posted for 'zpool events'. This value was carefully selected because for sd devices it implies that at least one timeout (SD_TIMEOUT) has occured. Unfortunately, even with FAILFAST set we may retry and request and not get an error. This behavior is strongly dependant on the device driver and how it is hooked in to the scsi error handling stack. However by setting the limit at 30s we can log the event even if no error was returned. Slightly longer term we can start recording these delays perhaps as a simple power-of-two histrogram. This histogram can then be reported as part of the 'zpool status' command when given an command line option. None of this code changes the internal behavior of ZFS. Currently it is simply for reporting excessively long delays.		2010-10-12 14:55:02 -07:00
..
avl	Support custom build directories and move includes	2010-09-08 12:38:56 -07:00
nvpair	Support custom build directories and move includes	2010-09-08 12:38:56 -07:00
unicode	Support custom build directories and move includes	2010-09-08 12:38:56 -07:00
zcommon	Support custom build directories and move includes	2010-09-08 12:38:56 -07:00
zfs	Initial zio delay timing	2010-10-12 14:55:02 -07:00
zpios	Support custom build directories and move includes	2010-09-08 12:38:56 -07:00
.gitignore	Add .gitignore files to exclude build products	2010-01-08 11:35:17 -08:00
Makefile.in	Support custom build directories and move includes	2010-09-08 12:38:56 -07:00