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/zfs-tests/include/tunables.cfg | |
| 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/zfs-tests/include/tunables.cfg')
| -rw-r--r-- | tests/zfs-tests/include/tunables.cfg | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/zfs-tests/include/tunables.cfg b/tests/zfs-tests/include/tunables.cfg index ad2811395..da7bc1613 100644 --- a/tests/zfs-tests/include/tunables.cfg +++ b/tests/zfs-tests/include/tunables.cfg @@ -82,6 +82,7 @@ VOL_INHIBIT_DEV UNSUPPORTED zvol_inhibit_dev VOL_MODE vol.mode zvol_volmode VOL_RECURSIVE vol.recursive UNSUPPORTED ZEVENT_LEN_MAX zevent.len_max zfs_zevent_len_max +ZEVENT_RETAIN_MAX zevent.retain_max zfs_zevent_retain_max ZIO_SLOW_IO_MS zio.slow_io_ms zio_slow_io_ms %%%% while read name FreeBSD Linux; do |