-
Notifications
You must be signed in to change notification settings - Fork 1.9k
ZTS: Fix replacement/resilver_restart_001 on FreeBSD #17279
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
Conversation
I wonder if it is actually the same problem as I see in #17269 -- "online" (re-)starts resilver asynchronously. |
Yes, they seem to be related. But I didn't go into the details for this fix. Increasing the size just resolved the |
@mcmilk I agree with @snajpa that it makes no logical sense to me. I don't have a particular problem with increasing the write size to 32MB, but I worry that the problem might re-appear later when we change something in CI or OS. I think some |
Decrease the RESILVER_MIN_TIME_MS variable from 50 to 20. So the test, which expects two 2 resilver starts will see them. Logfile of the seen failures before this fix: log: NOTE: expected 2 resilver start(s) after offline/online, found 1 log: expected 2 resilver start(s) after offline/online, found 1 The test time decreases also from around 00:42 to 00:24 seconds. Signed-off-by: Tino Reichardt <[email protected]> Closes: openzfs#16822
69139c8
to
4e2a990
Compare
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.
I still don't understand what and how does this fix, but if is does -- whatever, should not hurt.
Decrease the RESILVER_MIN_TIME_MS variable from 50 to 20. So the test, which expects two 2 resilver starts will see them. Logfile of the seen failures before this fix: log: NOTE: expected 2 resilver start(s) after offline/online, found 1 log: expected 2 resilver start(s) after offline/online, found 1 The test time decreases also from around 00:42 to 00:24 seconds. Reviewed-by: Tony Hutter <[email protected]> Reviewed-by: Alexander Motin <[email protected]> Signed-off-by: Tino Reichardt <[email protected]> Closes openzfs#16822 Closes openzfs#17279 (cherry picked from commit 3b18877)
Decrease the RESILVER_MIN_TIME_MS variable from 50 to 20. So the test, which expects two 2 resilver starts will see them. Logfile of the seen failures before this fix: log: NOTE: expected 2 resilver start(s) after offline/online, found 1 log: expected 2 resilver start(s) after offline/online, found 1 The test time decreases also from around 00:42 to 00:24 seconds. Reviewed-by: Tony Hutter <[email protected]> Reviewed-by: Alexander Motin <[email protected]> Signed-off-by: Tino Reichardt <[email protected]> Closes openzfs#16822 Closes openzfs#17279 (cherry picked from commit 3b18877)
Decrease the RESILVER_MIN_TIME_MS variable from 50 to 20. So the test, which expects two 2 resilver starts will see them. Logfile of the seen failures before this fix: log: NOTE: expected 2 resilver start(s) after offline/online, found 1 log: expected 2 resilver start(s) after offline/online, found 1 The test time decreases also from around 00:42 to 00:24 seconds. Reviewed-by: Tony Hutter <[email protected]> Reviewed-by: Alexander Motin <[email protected]> Signed-off-by: Tino Reichardt <[email protected]> Closes #16822 Closes #17279 (cherry picked from commit 3b18877)
Motivation and Context
Details on the issue can be seen here #16822
Increasing the data files from 16M to 32M fixes the replacement/resilver_restart_001 test.
Closes: #16822
Description
How Has This Been Tested?
Types of changes
Checklist:
Signed-off-by
.