-
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
ZTS: checkpoint_discard_busy does not set 16M on cleanup #16917
Conversation
Originally hex value is used as decimal. Signed-off-by: Toomas Soome <[email protected]>
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.
Better than nothing, but it would be better to restore the original value, as done by many other tests for other tunables, or even by zpool_wait_discard.ksh
for this one.
@tsoome amotin is correct - may I suggest (untested): diff --git a/tests/zfs-tests/tests/functional/pool_checkpoint/checkpoint_discard_busy.ksh b/tests/zfs-tests/tests/functional/pool_checkpoint/checkpoint_discard_busy.ksh
index 087aef902..58eb6e969 100755
--- a/tests/zfs-tests/tests/functional/pool_checkpoint/checkpoint_discard_busy.ksh
+++ b/tests/zfs-tests/tests/functional/pool_checkpoint/checkpoint_discard_busy.ksh
@@ -42,8 +42,7 @@ log_unsupported "Skipping, issue https://github.com/openzfs/zfs/issues/12053"
function test_cleanup
{
- # reset memory limit to 16M
- set_tunable64 SPA_DISCARD_MEMORY_LIMIT 1000000
+ restore_tunable SPA_DISCARD_MEMORY_LIMIT
cleanup_nested_pools
}
@@ -69,6 +68,7 @@ log_onexit test_cleanup
# map, we should have even more time to
# verify this.
#
+log_must save_tunable SPA_DISCARD_MEMORY_LIMIT
set_tunable64 SPA_DISCARD_MEMORY_LIMIT 128
log_must zpool checkpoint $NESTEDPOOL
@@ -102,7 +102,7 @@ log_mustnot zpool remove $NESTEDPOOL $FILEDISK1
log_mustnot zpool reguid $NESTEDPOOL
# reset memory limit to 16M
-set_tunable64 SPA_DISCARD_MEMORY_LIMIT 16777216
+restore_tunable SPA_DISCARD_MEMORY_LIMIT
nested_wait_discard_finish
|
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'm going to go ahead and merge this as is. We can follow up with the nicer fix which preserves and restores the value.
Originally hex value is used as decimal. Reviewed-by: Brian Behlendorf <[email protected]> Reviewed-by: Alexander Motin <[email protected]> Signed-off-by: Toomas Soome <[email protected]> Closes openzfs#16917
Originally hex value is used as decimal. Reviewed-by: Brian Behlendorf <[email protected]> Reviewed-by: Alexander Motin <[email protected]> Signed-off-by: Toomas Soome <[email protected]> Closes openzfs#16917
Originally hex value is used as decimal.
Motivation and Context
Description
Use correct decimal value for 16M.
How Has This Been Tested?
Types of changes
Checklist:
Signed-off-by
.