[LU-10906] checksums parameter not persistent after reboot

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.12.0
• Affects Version/s: Lustre 2.10.0
• Severity: 3
• Assignee: Emoly Liu
• Reporter: Andreas Dilger

Description

Attempting to run

mgs$ lctl set_param -P osc.s1lcl*.checksums=0

to disable checksums for their clients does not return any errors, and a

mgs$ lctl get_param osc.s1lcl*.checksums

shows that it is properly set to 0 at that time. However, after a reboot of a client node, this parameter gets reset to 1. This behavior does not appear for any of the other parameters that they are setting - just the checksums. There is something preventing the checksums parameter from being set permanently.

Issue Links

• is related to: LU-11058 sanity test_77k: checksum(1) != 0
• is related to: LU-8066 Move lustre procfs handling to sysfs and debugfs.
• is related to: LU-11011 checksum type can not be selected permanently