Details
-
Bug
-
Resolution: Fixed
-
Minor
-
Lustre 2.11.0
-
3
-
9223372036854775807
Description
conf-sanity test_76a fails to ‘/usr/sbin/lctl set_param -P osc.*.max_dirty_mb=64’. The last thing seen in the test_log is
Change MGS params max_dirty_mb: 32 new_max_dirty_mb: 64 CMD: trevis-50vm10 /usr/sbin/lctl set_param -P osc.*.max_dirty_mb=64 CMD: trevis-52vm7.trevis.hpdd.intel.com /usr/sbin/lctl get_param -n osc.*.max_dirty_mb | head -1 CMD: trevis-52vm7.trevis.hpdd.intel.com /usr/sbin/lctl get_param -n osc.*.max_dirty_mb | head -1 Waiting 90 secs for update CMD: trevis-52vm7.trevis.hpdd.intel.com /usr/sbin/lctl get_param -n osc.*.max_dirty_mb | head -1 … CMD: trevis-52vm7.trevis.hpdd.intel.com /usr/sbin/lctl get_param -n osc.*.max_dirty_mb | head -1 Update not seen after 90s: wanted '64' got '32' 32 conf-sanity test_76a: @@@@@@ FAIL: error while apply max_dirty_mb
On the MDS console and dmesg, we see that the command issues on the MGS/MDS is
[33955.881468] Lustre: DEBUG MARKER: trevis-50vm9.trevis.hpdd.intel.com: executing set_default_debug -1 all 4 [33965.425226] Lustre: DEBUG MARKER: /usr/sbin/lctl set_param -P osc.*.max_dirty_mb=64 [34056.950846] Lustre: DEBUG MARKER: /usr/sbin/lctl mark conf-sanity test_76a: @@@@@@ FAIL: error while apply max_dirty_mb
This test has failed with this error previously while testing the patch for LU-9325, https://review.whamcloud.com/#/c/30539/.
Logs for this failure are at
https://testing.hpdd.intel.com/test_sets/a77f2e70-3543-11e8-95c0-52540065bddc