aboutsummaryrefslogtreecommitdiffstats
path: root/tests/runfiles/linux.run
diff options
context:
space:
mode:
authorGeorge Wilson <[email protected]>2019-06-28 15:40:24 -0400
committerBrian Behlendorf <[email protected]>2019-06-28 12:40:23 -0700
commit681a85cb01a9f83b9f742d8fb634edddc68c5679 (patch)
tree039413ee05c67b4c4670d30161c3dbdefa552ff4 /tests/runfiles/linux.run
parent765d1f0644658d772addeb9b2dd5039ac43177ad (diff)
nopwrites on dmu_sync-ed blocks can result in a panic
After device removal, performing nopwrites on a dmu_sync-ed block will result in a panic. This panic can show up in two ways: 1. an attempt to issue an IOCTL in vdev_indirect_io_start() 2. a failed comparison of zio->io_bp and zio->io_bp_orig in zio_done() To resolve both of these panics, nopwrites of blocks on indirect vdevs should be ignored and new allocations should be performed on concrete vdevs. Reviewed-by: Igor Kozhukhov <[email protected]> Reviewed-by: Pavel Zakharov <[email protected]> Reviewed-by: Brian Behlendorf <[email protected]> Reviewed-by: Don Brady <[email protected]> Signed-off-by: George Wilson <[email protected]> Closes #8957
Diffstat (limited to 'tests/runfiles/linux.run')
-rw-r--r--tests/runfiles/linux.run2
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/runfiles/linux.run b/tests/runfiles/linux.run
index e5dd044ac..5d33b2058 100644
--- a/tests/runfiles/linux.run
+++ b/tests/runfiles/linux.run
@@ -763,7 +763,7 @@ tags = ['functional', 'refreserv']
pre =
tests = ['removal_all_vdev', 'removal_check_space',
'removal_condense_export', 'removal_multiple_indirection',
- 'removal_remap_deadlists',
+ 'removal_nopwrite', 'removal_remap_deadlists',
'removal_resume_export', 'removal_sanity', 'removal_with_add',
'removal_with_create_fs', 'removal_with_dedup',
'removal_with_errors', 'removal_with_export',