diff options
| author | Don Brady <[email protected]> | 2020-09-04 11:34:28 -0600 |
|---|---|---|
| committer | GitHub <[email protected]> | 2020-09-04 10:34:28 -0700 |
| commit | 4f0728278615eb42fc5022b2817c082f578e225f (patch) | |
| tree | 598cd2bb948dd3b0eb0469139a33269ae58fc40e /tests/runfiles/common.run | |
| parent | 3808032489f28c1f36b39c9a3274d5f4b6f9638a (diff) | |
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 <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Don Brady <[email protected]>
Closes #10861
Diffstat (limited to 'tests/runfiles/common.run')
| -rw-r--r-- | tests/runfiles/common.run | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/runfiles/common.run b/tests/runfiles/common.run index fcd968460..725afe2f0 100644 --- a/tests/runfiles/common.run +++ b/tests/runfiles/common.run @@ -346,7 +346,7 @@ tags = ['functional', 'cli_root', 'zpool_detach'] [tests/functional/cli_root/zpool_events] tests = ['zpool_events_clear', 'zpool_events_cliargs', 'zpool_events_follow', - 'zpool_events_poolname', 'zpool_events_errors'] + 'zpool_events_poolname', 'zpool_events_errors', 'zpool_events_duplicates'] tags = ['functional', 'cli_root', 'zpool_events'] [tests/functional/cli_root/zpool_export] |