Details
-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
9223372036854775807
Description
We need to have a sanity test that will hopefully prevent the repeated bugs that have been introduced by sysfs cleanup patches that result in config parameters being removed or renamed, a few of which have unfortunately made it into releases before they are caught.
The test should run "lctl list_param -R" on each of the client, mgs, mds1, and ost1 facets, strip out the fsname and OST/MDT/instance index unique values, "sort -u" the list so that it doesn't matter how many OSTs/MDTs there are, then compare it against a canonical list of parameters. It should be OK to have additional parameters (mostly this will happen if eg. both an MDT and OST are on the same node), but it should be a test failure if any parameters are removed (which will also catchy parameters that are renamed).