Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-10906

checksums parameter not persistent after reboot

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • Lustre 2.12.0
    • Lustre 2.10.0
    • None
    • 3
    • 9223372036854775807

      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.

            emoly.liu Emoly Liu
            adilger Andreas Dilger
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: