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

Set nodemap and add node range will cause Assertion

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • None
    • None
    • None
    • Centos OS 7.2 3.10.0-327.el7.x86_64
      ZFS 0.6.5.7
      Lustre 2.8.60_9_g35b5b07
    • 3
    • 9223372036854775807

    Description

      When I only add nodemap rule first time and set range to it. The assertion occurred. I also reformatted the MGT/MDT/OST many times, the situation was still the same. However, MGS/MDS was still alive and the nodemap rule is in the following:
      nodemap.b7e80612b9de478A.admin_nodemap=0
      nodemap.b7e80612b9de478A.deny_unknown=0
      nodemap.b7e80612b9de478A.exports=[

      ]
      nodemap.b7e80612b9de478A.fileset=/b7e80612-b9de-478A-bf61-6ed39dd318b2
      nodemap.b7e80612b9de478A.id=2
      nodemap.b7e80612b9de478A.idmap=[

      ]
      nodemap.b7e80612b9de478A.ranges=
      [

      { id: 2, start_nid: 10.8.8.9@o2ib1, end_nid: 10.8.8.9@o2ib1 }

      ]
      nodemap.b7e80612b9de478A.squash_gid=99
      nodemap.b7e80612b9de478A.squash_uid=99
      nodemap.b7e80612b9de478A.trusted_nodemap=0
      nodemap.default.admin_nodemap=0
      nodemap.default.exports=
      [

      { nid: 0@lo, uuid: hpcfs-MDT0000-lwp-MDT0000_UUID }

      ,

      { nid: 172.17.2.33@o2ib, uuid: hpcfs-MDT0000-lwp-OST0000_UUID }

      ,
      ]
      nodemap.default.id=0
      nodemap.default.squash_gid=99
      nodemap.default.squash_uid=99
      nodemap.default.trusted_nodemap=0

      172.17.x.x is my IB0 interface 10.8.x.x is IB0 partion(ib0.8xxx)

      Then asstion log is in the fllowing:
      Message from syslogd@oss1 at Nov 18 16:35:24 ...
      kernel:LustreError: 21843:0:(nodemap_handler.c:1428:nodemap_config_set_active()) ASSERTION( config->nmc_default_nodemap ) failed:

      Message from syslogd@oss1 at Nov 18 16:35:24 ...
      kernel:LustreError: 21843:0:(nodemap_handler.c:1428:nodemap_config_set_active()) LBUG

      Message from syslogd@oss1 at Nov 18 16:35:24 ...
      kernel:Kernel panic - not syncing: LBUG
      Sorry, I cannot catch more detail information about kernel panic

      Attachments

        Issue Links

          Activity

            People

              pjones Peter Jones
              sebg-crd-pm sebg-crd-pm (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: