-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cancel initialize and TRIM before vdev_metaslab_fini() #9751
Conversation
Any running 'zpool initialize' or TRIM must be cancelled prior to the vdev_metaslab_fini() call in spa_vdev_remove_log() which will unload the metaslabs and set ms->ms_group == NULL. TEST_ZTEST_TIMEOUT=7200 Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Issue openzfs#8602
3893945
to
4447e29
Compare
Codecov Report
@@ Coverage Diff @@
## master #9751 +/- ##
========================================
+ Coverage 80% 80% +<1%
========================================
Files 385 385
Lines 121302 121302
========================================
+ Hits 96442 96775 +333
+ Misses 24860 24527 -333
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like a reasonable cause and fix!
Thanks for your work on this issue, it was a pain when doing testing on zstd last few weeks!
I can confirm your testing is valid @behlendorf
While doing many runs of zstd for zstd last few weeks, it hits about 0.6 times in every push on buildbot.
A few hours of zloop on a faster machine would've atleast had one of these.
LGTM.
@ikozhukhov might want to review this. |
Any running 'zpool initialize' or TRIM must be cancelled prior to the vdev_metaslab_fini() call in spa_vdev_remove_log() which will unload the metaslabs and set ms->ms_group == NULL. Reviewed-by: Igor Kozhukhov <igor@dilos.org> Reviewed-by: Kjeld Schouten <kjeld@schouten-lebbing.nl> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes openzfs#8602 Closes openzfs#9751
Any running 'zpool initialize' or TRIM must be cancelled prior to the vdev_metaslab_fini() call in spa_vdev_remove_log() which will unload the metaslabs and set ms->ms_group == NULL. Reviewed-by: Igor Kozhukhov <igor@dilos.org> Reviewed-by: Kjeld Schouten <kjeld@schouten-lebbing.nl> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes openzfs#8602 Closes openzfs#9751
Any running 'zpool initialize' or TRIM must be cancelled prior to the vdev_metaslab_fini() call in spa_vdev_remove_log() which will unload the metaslabs and set ms->ms_group == NULL. Reviewed-by: Igor Kozhukhov <igor@dilos.org> Reviewed-by: Kjeld Schouten <kjeld@schouten-lebbing.nl> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes openzfs#8602 Closes openzfs#9751
Any running 'zpool initialize' or TRIM must be cancelled prior to the vdev_metaslab_fini() call in spa_vdev_remove_log() which will unload the metaslabs and set ms->ms_group == NULL. Reviewed-by: Igor Kozhukhov <igor@dilos.org> Reviewed-by: Kjeld Schouten <kjeld@schouten-lebbing.nl> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes #8602 Closes #9751
Motivation and Context
Resolve #8602 which is one of the more common ztest failures
encountered by the CI.
Description
Any running
zpool initialize
or TRIM must be cancelled priorto the
vdev_metaslab_fini()
call in spa_vdev_remove_log() whichwill unload the metaslabs and set ms->ms_group == NULL.
How Has This Been Tested?
Unfortunately, I've been unable to consistently reproduce this
issue locally. I've run
ztest
with this PR applied for severalhours and was unable to reproduce the issue. However, since the
CI does relatively frequently hit this issue I've opened this PR for
additional testing and increased the ztest run time to 2 hours.
Types of changes
Checklist:
Signed-off-by
.