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

          Activity

            [LU-9154] MDS Nodemap filset will be clear to empty after add new nodemap

            Close as a duplicate of LU-10703, since that has a patch.

            adilger Andreas Dilger added a comment - Close as a duplicate of LU-10703 , since that has a patch.
            emoly.liu Emoly Liu added a comment -

            This issue is a duplicate of LU-10703. I created a patch at https://review.whamcloud.com/31450 .

            emoly.liu Emoly Liu added a comment - This issue is a duplicate of LU-10703 . I created a patch at https://review.whamcloud.com/31450 .

            Hi mhaakddn ,

            *Is there *any further update?

            sebg-crd-pm sebg-crd-pm (Inactive) added a comment - Hi  mhaakddn  , *Is there *any further update?

            I am seeing this issue in production with a Lustre 2.10.x system

            ON MDS0: lctl set_param -P nodemap.test.fileset='/filesystem/test/path'

            ON ADMIN NODE: cexec -p mds: 'lctl get_param nodemap.test.fileset'
            mds0: }}{{nodemap.test.fileset=/filesystem/test/path
            mds1: }}{{nodemap.test.fileset=/filesystem/test/path
            mds2: }}{{nodemap.test.fileset=/filesystem/test/path
            mds3: }}{{nodemap.test.fileset=/filesystem/test/path

            ON ADMIN NODE: cexec -p oss: 'lctl get_param nodemap.test.fileset'
            oss0: }}{{nodemap.test.fileset=/filesystem/test/path
            oss1: }}{{nodemap.test.fileset=/filesystem/test/path
            .............

            ON MDS0: lctl set_param nodemap.active=1

            ON ADMIN NODE: cexec -p mds: 'lctl get_param nodemap.test.fileset'
            mds0: }}{{nodemap.test.fileset=
            mds1: }}{{nodemap.test.fileset=
            mds2: }}{{nodemap.test.fileset=
            mds3: }}{{nodemap.test.fileset=

            ON ADMIN NODE: cexec -p oss: 'lctl get_param nodemap.test.fileset'
            oss0: }}{{nodemap.test.fileset=
            oss1: }}{{nodemap.test.fileset=
            .............

            Hope this helps.

            It looks like its quite broken.

            Also I'm about to lodge another case because setting fileset twice on the same nodemap kills the MGS.

            We found that because we tried to enable nodemaps, it cleared the fileset value and we tried setting it again.

            mhaakddn Malcolm Haak - NCI (Inactive) added a comment - I am seeing this issue in production with a Lustre 2.10.x system ON MDS0: lctl set_param -P nodemap.test.fileset='/filesystem/test/path' ON ADMIN NODE: cexec -p mds: 'lctl get_param nodemap.test.fileset' mds0: }}{{nodemap.test.fileset=/filesystem/test/path mds1: }}{{nodemap.test.fileset=/filesystem/test/path mds2: }}{{nodemap.test.fileset=/filesystem/test/path mds3: }}{{nodemap.test.fileset=/filesystem/test/path ON ADMIN NODE: cexec -p oss: 'lctl get_param nodemap.test.fileset' oss0: }}{{nodemap.test.fileset=/filesystem/test/path oss1: }}{{nodemap.test.fileset=/filesystem/test/path ............. ON MDS0: lctl set_param nodemap.active=1 ON ADMIN NODE: cexec -p mds: 'lctl get_param nodemap.test.fileset' mds0: }}{{nodemap.test.fileset= mds1: }}{{nodemap.test.fileset= mds2: }}{{nodemap.test.fileset= mds3: }}{{nodemap.test.fileset= ON ADMIN NODE: cexec -p oss: 'lctl get_param nodemap.test.fileset' oss0: }}{{nodemap.test.fileset= oss1: }}{{nodemap.test.fileset= ............. Hope this helps. It looks like its quite broken. Also I'm about to lodge another case because setting fileset twice on the same nodemap kills the MGS. We found that because we tried to enable nodemaps, it cleared the fileset value and we tried setting it again.

            Hi Emoly,
            Is it ok to reproduce this issue by build-LU9154.sh/nodemap-LU915.sh ?

            sebg-crd-pm sebg-crd-pm (Inactive) added a comment - Hi Emoly, Is it ok to reproduce this issue by build-LU9154.sh/nodemap-LU915.sh ?

            nodemap-LU9154.sh build-LU9154.sh
            Hi Emoly,
            I simplified the my build lustre steps and nodemap test scripts.
            The issue can be reprodced in my site only execute these 2 scripts.

            build-LU9154.sh
            create 3 nodes lustre system(based on zfs) , mgs:mdsb1, mds:mdsb2, oss:ossb1
            nodemap-LU915.sh
            create nodemapA( set fileset) then create nodemapB =>mds nodemapA fileset missing

            sebg-crd-pm sebg-crd-pm (Inactive) added a comment - nodemap-LU9154.sh build-LU9154.sh Hi Emoly, I simplified the my build lustre steps and nodemap test scripts. The issue can be reprodced in my site only execute these 2 scripts. build-LU9154.sh create 3 nodes lustre system(based on zfs) , mgs:mdsb1, mds:mdsb2, oss:ossb1 nodemap-LU915.sh create nodemapA( set fileset) then create nodemapB =>mds nodemapA fileset missing
            emoly.liu Emoly Liu added a comment -

            If possible, please post all the steps you did to reproduce this issue. Thanks.

            emoly.liu Emoly Liu added a comment - If possible, please post all the steps you did to reproduce this issue. Thanks.

            Emoly,

            I have set lctl set_param debug=-1 then test it again.
            Thereis somethiong wrong. (This log get form mds. ) Should I get something else?

            Jun 16 22:01:28 mdsb2 kernel: Lustre: 31848:0:(nodemap_handler.c:1020:nodemap_create()) adding nodemap 'nodemap1' to config without default nodemap
            Jun 16 22:01:28 mdsb2 kernel: Lustre: 31848:0:(nodemap_handler.c:1020:nodemap_create()) Skipped 1 previous similar message
            Jun 16 22:05:01 mdsb2 kernel: LustreError: 32302:0:(nodemap_storage.c:404:nodemap_idx_nodemap_update()) cannot add nodemap config to non-existing MGS.

            sebg-crd-pm sebg-crd-pm (Inactive) added a comment - Emoly, I have set lctl set_param debug=-1 then test it again. Thereis somethiong wrong. (This log get form mds. ) Should I get something else? Jun 16 22:01:28 mdsb2 kernel: Lustre: 31848:0:(nodemap_handler.c:1020:nodemap_create()) adding nodemap 'nodemap1' to config without default nodemap Jun 16 22:01:28 mdsb2 kernel: Lustre: 31848:0:(nodemap_handler.c:1020:nodemap_create()) Skipped 1 previous similar message Jun 16 22:05:01 mdsb2 kernel: LustreError: 32302:0:(nodemap_storage.c:404:nodemap_idx_nodemap_update()) cannot add nodemap config to non-existing MGS.

            I have test 2.9.0 and it also have the same problem.
            Did you set nodemap.active ? I test it with "lctl set_param nodemap.active=1"

            sebg-crd-pm sebg-crd-pm (Inactive) added a comment - I have test 2.9.0 and it also have the same problem. Did you set nodemap.active ? I test it with "lctl set_param nodemap.active=1"
            emoly.liu Emoly Liu added a comment -

            I used 2.9.53 in my local test and 2.9.0 in multiple nodes test.

            emoly.liu Emoly Liu added a comment - I used 2.9.53 in my local test and 2.9.0 in multiple nodes test.

            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: