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

Nodemap: Multiple entries reported for the same client export

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.17.0
    • Lustre 2.16.0, Lustre 2.17.0
    • 3
    • 9223372036854775807

    Description

      Under certain conditions, lctl get_param nodemap.<nm>.exports reports multiple entries for seemingly the same export and UUID:

      nodemap.tenant.exports=
      [
       { nid: 192.155.155.50@tcp, uuid: 81d25e02-14c0-46fa-9054-590b7949ecb8 },
       { nid: 192.155.155.50@tcp, uuid: 81d25e02-14c0-46fa-9054-590b7949ecb8 },
       { nid: 192.155.155.50@tcp, uuid: 81d25e02-14c0-46fa-9054-590b7949ecb8 },
       { nid: 192.155.155.50@tcp, uuid: 81d25e02-14c0-46fa-9054-590b7949ecb8 }
      ]
      

      This can occur for multiple MDTs or multiple OSTs because each *obd_connect() (for MDT and OST) adds the export as a member to the corresponding nodemap. This is expected, but there is no duplication check when printing the exports of anodemap. Therefore, several exports with the same UUID can be printed when listing them with lctl get_param.

      Attachments

        Activity

          People

            mvef Marc Vef
            mvef Marc Vef
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: