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

Can't mount MGS due to label being less than 8 characters long.

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • Lustre 2.7.0
    • Lustre 2.7.0
    • 3
    • 16404

    Description

      The patch for LU-5383 fixed a out bound for ldd_svname. It test to see if ldd_svname is at least 8 characters in length but the function in lustre_disk.h server_make_name() sets ldd_svname for the mgs to MGS which is to short. This can prevent the MGS from mounting.

      Attachments

        Issue Links

          Activity

            [LU-5863] Can't mount MGS due to label being less than 8 characters long.
            pjones Peter Jones added a comment -

            Landed for 2.7

            pjones Peter Jones added a comment - Landed for 2.7

            Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/13391/
            Subject: LU-5863 tests: add a separate MGS/MDS test case into conf-sanity
            Project: fs/lustre-release
            Branch: master
            Current Patch Set:
            Commit: 589d93f8b01f0a923c0f6ebb64c7ad9935fb05da

            gerrit Gerrit Updater added a comment - Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/13391/ Subject: LU-5863 tests: add a separate MGS/MDS test case into conf-sanity Project: fs/lustre-release Branch: master Current Patch Set: Commit: 589d93f8b01f0a923c0f6ebb64c7ad9935fb05da
            yujian Jian Yu added a comment -

            Thank you Patrick and James for the information. The work to enhance autotest system is tracked in TEI-91. For this ticket, I pushed the above patch to add a test case into conf-sanity.sh to verify separate MGS/MDS. The new test case will not be skipped under autotest combined MGS/MDS configuration.

            yujian Jian Yu added a comment - Thank you Patrick and James for the information. The work to enhance autotest system is tracked in TEI-91. For this ticket, I pushed the above patch to add a test case into conf-sanity.sh to verify separate MGS/MDS. The new test case will not be skipped under autotest combined MGS/MDS configuration.

            Jian Yu (jian.yu@intel.com) uploaded a new patch: http://review.whamcloud.com/13391
            Subject: LU-5863 tests: add a separate MGS/MDS test case into conf-sanity
            Project: fs/lustre-release
            Branch: master
            Current Patch Set: 1
            Commit: 41231258e22cb35555e17a8b94d80c7bfdc5522d

            gerrit Gerrit Updater added a comment - Jian Yu (jian.yu@intel.com) uploaded a new patch: http://review.whamcloud.com/13391 Subject: LU-5863 tests: add a separate MGS/MDS test case into conf-sanity Project: fs/lustre-release Branch: master Current Patch Set: 1 Commit: 41231258e22cb35555e17a8b94d80c7bfdc5522d

            Same here. ORNL has run separate MGS/MDS servers for years. If I remember right running separate MGS/MDS is required for IR to work properly.

            simmonsja James A Simmons added a comment - Same here. ORNL has run separate MGS/MDS servers for years. If I remember right running separate MGS/MDS is required for IR to work properly.

            In case it influences the decision to know what people are doing in the real world, Cray is increasingly using separate MGS and MDS volumes for ease of backup and recovery.
            Also for DNE - it's convenient to have MDS volumes all identical.

            paf Patrick Farrell (Inactive) added a comment - In case it influences the decision to know what people are doing in the real world, Cray is increasingly using separate MGS and MDS volumes for ease of backup and recovery. Also for DNE - it's convenient to have MDS volumes all identical.
            yujian Jian Yu added a comment -

            Hi Andreas,

            Clearly, we need a conf-sanity test that formats a separate MGS and mounts it, since we can't possibly have had such a test if this bug slipped through.

            I found that conf-sanity test 21d is a basic test case that starting a separate MGS. However, autotest system always uses the configuration of combined MGT and MDT, and then test 21d has been always skipped. Should we enhance autotest system to add a configuration of separated MGT and MDT, and run a test session with this configuration?
            For now and this ticket, I'll just add a new test case that formats $fs2mds_DEV as a separate MGT and mounts it.

            yujian Jian Yu added a comment - Hi Andreas, Clearly, we need a conf-sanity test that formats a separate MGS and mounts it, since we can't possibly have had such a test if this bug slipped through. I found that conf-sanity test 21d is a basic test case that starting a separate MGS. However, autotest system always uses the configuration of combined MGT and MDT, and then test 21d has been always skipped. Should we enhance autotest system to add a configuration of separated MGT and MDT, and run a test session with this configuration? For now and this ticket, I'll just add a new test case that formats $fs2mds_DEV as a separate MGT and mounts it.
            yujian Jian Yu added a comment -

            Sure. I'll do.

            yujian Jian Yu added a comment - Sure. I'll do.

            Could you finish it off. I'm working on a few other tickets.

            simmonsja James A Simmons added a comment - Could you finish it off. I'm working on a few other tickets.
            yujian Jian Yu added a comment -

            Hi James Simmons,
            Are you going to add a regression test case into conf-sanity.sh or would you like me to do this?

            yujian Jian Yu added a comment - Hi James Simmons, Are you going to add a regression test case into conf-sanity.sh or would you like me to do this?

            People

              jamesanunez James Nunez (Inactive)
              simmonsja James A Simmons
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: