Don Brady 8afac5dc55 Avoid posting duplicate zpool events ... Duplicate io and checksum ereport events can misrepresent that things are worse than they seem. Ideally the zpool events and the corresponding vdev stat error counts in a zpool status should be for unique errors -- not the same error being counted over and over. This can be demonstrated in a simple example. With a single bad block in a datafile and just 5 reads of the file we end up with a degraded vdev, even though there is only one unique error in the pool. The proposed solution to the above issue, is to eliminate duplicates when posting events and when updating vdev error stats. We now save recent error events of interest when posting events so that we can easily check for duplicates when posting an error. Reviewed by: Brad Lewis <brad.lewis@delphix.com> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Don Brady <don.brady@delphix.com> Closes #10861		2020-09-09 10:26:00 -07:00
..
fs	Avoid posting duplicate zpool events	2020-09-09 10:26:00 -07:00
Makefile.am	Avoid installing kernel headers on FreeBSD	2020-06-27 17:40:14 -07:00
protocol.h	Update build system and packaging	2018-05-29 16:00:33 -07:00
util.h	Avoid posting duplicate zpool events	2020-09-09 10:26:00 -07:00