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

test: lfsck FAIL: lfsck returned 127, should be <= 1

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.4.0
    • Lustre 2.3.0, Lustre 2.1.3
    • None
    • 3
    • 6004

    Description

      This test failed in both 2.3.0 client and 2.1.3 client.

      It failed because the test suite try to execute lfsck at the client, which does not have e2fsprogs rpm installed and caused "command not found" error: (see dmsg log of service331)
      lfsck -c -l --mdsdb /var/acc-sm-shared/mdsdb --ostdb /var/acc-sm-shared/ostdb-0 /var/acc-sm-shared/ostdb-1 /mnt/nbp0-1
      /usr/lib64/lustre/tests/test-framework.sh: line 3246: lfsck: command not found
      lfsck : @@@@@@ FAIL: lfsck -c -l --mdsdb /var/acc-sm-shared/mdsdb --ostdb /var/acc-sm-shared/ostdb-0 /var/acc-sm-shared/ostdb-1 /mnt/nbp0-1 returned 127, should be <= 1

      The return code '127' is when command not found.

      If I allow the return code to be either <= 1 or equals to 127, the test suite would complete. I do not understand why the test suite that tries to execute lfsck on client. If e2fsprogs rpm is not required on clients, the test is flawed.

      Test_logs tarball is attached.

      Attachments

        Activity

          [LU-2571] test: lfsck FAIL: lfsck returned 127, should be <= 1
          pjones Peter Jones made changes -
          Fix Version/s New: Lustre 2.4.0 [ 10154 ]
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          pjones Peter Jones added a comment -

          Landed for 2.4

          pjones Peter Jones added a comment - Landed for 2.4
          emoly.liu Emoly Liu added a comment -

          Jay, the patch is ready for landing. Oleg, will we land it soon?

          emoly.liu Emoly Liu added a comment - Jay, the patch is ready for landing. Oleg, will we land it soon?

          If you guys feel no need to address this issue, I am OK you close this bug. I have changed my setup to always include /usr/sbin/lfsck in my environment.

          jaylan Jay Lan (Inactive) added a comment - If you guys feel no need to address this issue, I am OK you close this bug. I have changed my setup to always include /usr/sbin/lfsck in my environment.
          emoly.liu Emoly Liu added a comment - Patch at http://review.whamcloud.com/#change,5139

          If the fikesystem is mounted on the MDS this would allow LFSCK lfsck to be run there.

          adilger Andreas Dilger added a comment - If the fikesystem is mounted on the MDS this would allow LFSCK lfsck to be run there.
          emoly.liu Emoly Liu added a comment -

          Usually we install e2fsprogs rpm on all the nodes by default and run lfsck on client. But, I agree that it's not necessary to have e2fsprogs rpm on clients.

          I have some ideas to fix this check:
          1. only install lfsck on client, instead of the whole e2fsprogs rpm, and
          2. let me check if we can run lfsck on server and then modify the test script.

          Andreas, do you have any advice?

          emoly.liu Emoly Liu added a comment - Usually we install e2fsprogs rpm on all the nodes by default and run lfsck on client. But, I agree that it's not necessary to have e2fsprogs rpm on clients. I have some ideas to fix this check: 1. only install lfsck on client, instead of the whole e2fsprogs rpm, and 2. let me check if we can run lfsck on server and then modify the test script. Andreas, do you have any advice?
          emoly.liu Emoly Liu made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          emoly.liu Emoly Liu added a comment -

          OK, I will have a look.

          emoly.liu Emoly Liu added a comment - OK, I will have a look.
          pjones Peter Jones made changes -
          Assignee Original: WC Triage [ wc-triage ] New: Emoly Liu [ emoly.liu ]

          People

            emoly.liu Emoly Liu
            jaylan Jay Lan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: