diff options
| author | Brian Behlendorf <[email protected]> | 2018-08-31 15:30:44 -0700 |
|---|---|---|
| committer | GitHub <[email protected]> | 2018-08-31 15:30:44 -0700 |
| commit | bb91178e60df553071ce2e18b0067ef703f7b583 (patch) | |
| tree | 96e1c6c75c0fc58f72bb54b6cdbc11a376081c31 /tests/test-runner | |
| parent | e927fc8a522e1c0db89955cc555841aa23bbd634 (diff) | |
ZTS: Fix EBUSY volume destroy failures
It's possible for an unrelated process, like blkid, to have the
volume open when 'zfs destroy' is run. Switch the cleanup functions
to the destroy_dataset() helper which handles this case by retrying
the destroy when the dataset is busy. This was done not only for
volumes but also for file systems for consistency.
Reviewed-by: Richard Elling <[email protected]>
Reviewed-by: George Melikov <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes #7854
Diffstat (limited to 'tests/test-runner')
| -rwxr-xr-x | tests/test-runner/bin/zts-report.py | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/tests/test-runner/bin/zts-report.py b/tests/test-runner/bin/zts-report.py index e1a9011d3..5747f1422 100755 --- a/tests/test-runner/bin/zts-report.py +++ b/tests/test-runner/bin/zts-report.py @@ -216,8 +216,6 @@ maybe = { 'cli_root/zdb/zdb_006_pos': ['FAIL', known_reason], 'cli_root/zfs_get/zfs_get_004_pos': ['FAIL', known_reason], 'cli_root/zfs_get/zfs_get_009_pos': ['SKIP', '5479'], - 'cli_root/zfs_receive/receive-o-x_props_override': - ['FAIL', known_reason], 'cli_root/zfs_rename/zfs_rename_006_pos': ['FAIL', '5647'], 'cli_root/zfs_rename/zfs_rename_009_neg': ['FAIL', '5648'], 'cli_root/zfs_rollback/zfs_rollback_001_pos': ['FAIL', '6415'], |