[LU-6688] sanityn 77a and 77b fail to set the NRS policy

Related — Thu, 18 Aug 2016 17:28:26 +0000

Both sanityn test 77a and 77b set the NRS policy on the MDS:

test_77a() { #LU-3266
        do_facet $SINGLEMDS lctl set_param ost.OSS.*.nrs_policies="fifo"
…
}
run_test 77a "check FIFO NRS policy"


test_77b() { #LU-3266
        do_facet $SINGLEMDS lctl set_param ost.OSS.*.nrs_policies="crrn"
        do_facet $SINGLEMDS lctl set_param ost.OSS.*.nrs_crrn_quantum=1

…
}
run_test 77b "check CRR-N NRS policy"

The calls to ‘lctl set_param $SINGLEMDS’ are silently failing. In the client test logs, we see:

== sanityn test 77a: check FIFO NRS policy == 11:19:01 (1433416741)
CMD: shadow-25vm4 lctl set_param ost.OSS.*.nrs_policies=fifo
shadow-25vm4: error: set_param: ost/OSS/*/nrs_policies: Found no match

and

== sanityn test 77b: check CRR-N NRS policy == 11:19:17 (1433416757)
CMD: shadow-25vm4 lctl set_param ost.OSS.*.nrs_policies=crrn
shadow-25vm4: error: set_param: ost/OSS/*/nrs_policies: Found no match
CMD: shadow-25vm4 lctl set_param ost.OSS.*.nrs_crrn_quantum=1
shadow-25vm4: error: set_param: ost/OSS/*/nrs_crrn_quantum: Found no match
policy: crr-n, crrn_quantum 1
CMD: shadow-25vm5,shadow-25vm6.shadow.whamcloud.com sync
CMD: shadow-25vm4 lctl set_param ost.OSS.*.nrs_crrn_quantum=64
shadow-25vm4: error: set_param: ost/OSS/*/nrs_crrn_quantum: Found no match
policy: crr-n, crrn_quantum 64

One example of test logs with these errors is at https://testing.hpdd.intel.com/test_sets/3f006138-0ad1-11e5-88ab-5254006e85c2

The problem is, looking on the MDS, there is no /proc/fs/lustre/ost directory.

Since these test are only setting the NRS policy and writing data to files, it may not matter if the NRS policy is set on the MDS(s) or OST(s).

Whamcloud Community JIRA

[LU-6688] sanityn 77a and 77b fail to set the NRS policy