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

Interop 2.4.0<->2.5 failure on test suite sanity test_129: return code 28 received instead of expected 27

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.6.0, Lustre 2.5.1
    • Lustre 2.5.0
    • client: 2.4.0
      server: lustre-master build #1652
    • 3
    • 10305

    Description

      This issue was created by maloo for sarah <sarah@whamcloud.com>

      This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/9fb64ab0-15be-11e3-a83f-52540035b04c.

      The sub-test test_129 failed with the following error:

      return code 28 received instead of expected 27

      Cannot find useful log

      Attachments

        Issue Links

          Activity

            [LU-3909] Interop 2.4.0<->2.5 failure on test suite sanity test_129: return code 28 received instead of expected 27
            yujian Jian Yu added a comment -

            That will cause this test to fail on newer kernels I think?

            In set_dir_limits():

                    local LDPROC=/proc/fs/ldiskfs
                    #......
            
                            do_facet $facet "test -e $LDPROC/$canondev/max_dir_size" ||
                                                            LDPROC=/sys/fs/ldiskfs
            

            If "/proc/fs/ldiskfs" does not exist, "/sys/fs/ldiskfs" will be used.

            yujian Jian Yu added a comment - That will cause this test to fail on newer kernels I think? In set_dir_limits(): local LDPROC=/proc/fs/ldiskfs #...... do_facet $facet "test -e $LDPROC/$canondev/max_dir_size" || LDPROC=/sys/fs/ldiskfs If "/proc/fs/ldiskfs" does not exist, "/sys/fs/ldiskfs" will be used.

            I noticed that on my system the max_dir_size tunable is /sys/fs/ldiskfs/

            {dev}/max_dir_size instead of /proc/fs/ldiskfs/{dev}

            /max_dir_size. That will cause this test to fail on newer kernels I think?

            adilger Andreas Dilger added a comment - I noticed that on my system the max_dir_size tunable is /sys/fs/ldiskfs/ {dev}/max_dir_size instead of /proc/fs/ldiskfs/{dev} /max_dir_size. That will cause this test to fail on newer kernels I think?
            pjones Peter Jones added a comment -

            Landed for 2.6. Should land to b2_5 shortly

            pjones Peter Jones added a comment - Landed for 2.6. Should land to b2_5 shortly
            yujian Jian Yu added a comment -

            Lustre client build: http://build.whamcloud.com/job/lustre-b2_5/5/
            Lustre server build: http://build.whamcloud.com/job/lustre-b2_4/70/ (2.4.2)

            The same failure occurred:
            https://maloo.whamcloud.com/test_sets/a8e2dbf8-74f5-11e3-95ae-52540035b04c

            Here is the back-ported patch for Lustre b2_5 branch: http://review.whamcloud.com/#/c/8727/

            yujian Jian Yu added a comment - Lustre client build: http://build.whamcloud.com/job/lustre-b2_5/5/ Lustre server build: http://build.whamcloud.com/job/lustre-b2_4/70/ (2.4.2) The same failure occurred: https://maloo.whamcloud.com/test_sets/a8e2dbf8-74f5-11e3-95ae-52540035b04c Here is the back-ported patch for Lustre b2_5 branch: http://review.whamcloud.com/#/c/8727/
            yujian Jian Yu added a comment - Lustre client build: http://build.whamcloud.com/job/lustre-b2_4/70/ (2.4.2) Lustre server build: http://build.whamcloud.com/job/lustre-b2_5/5/ The same failure occurred: https://maloo.whamcloud.com/test_sets/5584c4fa-755c-11e3-95ae-52540035b04c

            3rd version is uploaded.
            'lctl get_param' is used to get mds blocksize as Andreas suggested.

            Please, take a look
            http://review.whamcloud.com/8143

            vsaveliev Vladimir Saveliev added a comment - 3rd version is uploaded. 'lctl get_param' is used to get mds blocksize as Andreas suggested. Please, take a look http://review.whamcloud.com/8143

            new version is uploaded, please, take a look
            http://review.whamcloud.com/8143

            vsaveliev Vladimir Saveliev added a comment - new version is uploaded, please, take a look http://review.whamcloud.com/8143

            Patch needs to be rebased

            cliffw Cliff White (Inactive) added a comment - Patch needs to be rebased

            The problem seems to be caused by changes of max dir size limit logic. The below patch is to fix that. Please take a look.
            http://review.whamcloud.com/8143

            For correct work the following patch from https://jira.hpdd.intel.com/browse/LU-2479 is needed:
            http://review.whamcloud.com/8137

            vsaveliev Vladimir Saveliev added a comment - The problem seems to be caused by changes of max dir size limit logic. The below patch is to fix that. Please take a look. http://review.whamcloud.com/8143 For correct work the following patch from https://jira.hpdd.intel.com/browse/LU-2479 is needed: http://review.whamcloud.com/8137
            sarah Sarah Liu added a comment -

            Also hit this error between 2.4.0 server and 2.5 client:
            https://maloo.whamcloud.com/test_sets/f5eae562-19c4-11e3-bb73-52540035b04c

            sarah Sarah Liu added a comment - Also hit this error between 2.4.0 server and 2.5 client: https://maloo.whamcloud.com/test_sets/f5eae562-19c4-11e3-bb73-52540035b04c

            People

              cliffw Cliff White (Inactive)
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: