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

Unsupported parameter mds_attr_cpu_bind error when updating from a 2.12 LTS release to master

Details

    • Bug
    • Resolution: Not a Bug
    • Major
    • None
    • Upstream
    • None
    • 3
    • 9223372036854775807

    Description

      When updating from 2.12 (LTS) to latest master, I get the following unsupported parameter error:

      [  495.249412] mdt: Unknown parameter `mds_attr_cpu_bind'
[  495.262504] LustreError: 158-c: Can't load module 'mdt'

      Are parameters such as these supported from one LTS to the next (i.e. 2.15)?

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. LU-13326 remove MDS_SETATTR_PORTAL on MDS

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            [LU-15084] Unsupported parameter mds_attr_cpu_bind error when updating from a 2.12 LTS release to master
            koutoupis Petros Koutoupis added a comment -

            @Andreas Dilger, I spoke with my team and they provided me with the history on why it was part of our configuration and why it may not have been immediately removed. Thank you for your input. I will close this issue.

            koutoupis Petros Koutoupis added a comment - @Andreas Dilger, I spoke with my team and they provided me with the history on why it was part of our configuration and why it may not have been immediately removed. Thank you for your input. I will close this issue.
            adilger Andreas Dilger added a comment -

            This attribute has done nothing since Lustre 2.1, according to my LU-13326 patch that removes it. Was there a reason this module parameter was being used?

            Typically I'm on the side of maintaining compatibility, but this is totally safe to remove from the 2.12 LTS system before the upgrade without any loss of functionality, so I'm not sure what benefit there would be to keeping compatibility?

            adilger Andreas Dilger added a comment - This attribute has done nothing since Lustre 2.1, according to my LU-13326 patch that removes it. Was there a reason this module parameter was being used? Typically I'm on the side of maintaining compatibility, but this is totally safe to remove from the 2.12 LTS system before the upgrade without any loss of functionality, so I'm not sure what benefit there would be to keeping compatibility?

            People

              wc-triage WC Triage
              koutoupis Petros Koutoupis
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: