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

MDS Nodemap filset will be clear to empty after add new nodemap

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • None
    • None
    • None
    • Centos 7.2.3.10.0-327.22.2.el7.x86_64
      Lustre 2.8.59_25_g40e3986
      ZFS 0.6.5.7
    • 3
    • 9223372036854775807

    Description

      I have one nodemapA and set fileset by "lctl set_param -P xxxx".
      The nodemapA fileset in MDS will be clear to empty when do
      "lctl nodemap_add_range --name nodemapA --range xxx" or "lctl nodemap_add nodemapB"
      But the nodemapA fileset still exist in MGS. Does anyone have the same problem? Thanks.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. LU-10703 All mds Nodemap filset will be cleared when do some nodemap operations (lustre 2.10.3)

          • Major - Major loss of function.
          • Resolved

          Activity

            [LU-9154] MDS Nodemap filset will be clear to empty after add new nodemap
            adilger Andreas Dilger made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            emoly.liu Emoly Liu made changes -
            Link New: This issue is duplicated by LU-10703 [ LU-10703 ]
            sebg-crd-pm sebg-crd-pm (Inactive) made changes -
            Attachment New: nodemap-LU9154.sh [ 27061 ]
            Attachment New: build-LU9154.sh [ 27062 ]
            pjones Peter Jones made changes -
            Assignee Original: WC Triage [ wc-triage ] New: Emoly Liu [ emoly.liu ]
            sebg-crd-pm sebg-crd-pm (Inactive) created issue -

            People

              emoly.liu Emoly Liu
              sebg-crd-pm sebg-crd-pm (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: