Enable all ztest functions for expandable raidz #39
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fuporovvStack
changed the title
|
Outdated because of: openzfs@5caeef0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The proposed version of ztest is free from bp checksum corruptions. It was verified by several hundreds hours of ztest running.
The 16 or 32 ztest utility processes are started in parallel with zpools on tmpfs, ztest failures with asserts triggering are ignored.
The average number of core dumps per 6 hours ztest testing is near 5 - 10.
Some of triggered asserts:
#38
All ztest functions enabled excluding ztest_vdev_attach_detach, which skipped for now because of issue:
#37