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

sanity test_129: current dir size 24576, previous limit 24576

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • Lustre 2.8.0, Lustre 2.10.0
    • Lustre 2.8.0
    • None
    • EL7.1 Server/EL7.1 Client - DNE
      Master, build# 3270
    • 3
    • 9223372036854775807

    Description

      This issue was created by maloo for Saurabh Tandan <saurabh.tandan@intel.com>

      This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/3eac1b80-a26d-11e5-bdef-5254006e85c2.

      The sub-test test_129 failed with the following error:

      CMD: shadow-53vm3 test -e /sys/fs/ldiskfs/dm-3/max_dir_size
      CMD: shadow-53vm3 echo 0 >/sys/fs/ldiskfs/dm-3/max_dir_size
      return code 28 received as expected
      current dir size 24576, previous limit 24576
      

      Appears to be similar to LU-2479

      Attachments

        Issue Links

          Activity

            [LU-7584] sanity test_129: current dir size 24576, previous limit 24576

            Patch has landed for 2.8

            jgmitter Joseph Gmitter (Inactive) added a comment - Patch has landed for 2.8

            Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/18192/
            Subject: LU-7584 tests: create file on single MDS in sanity test 129
            Project: fs/lustre-release
            Branch: master
            Current Patch Set:
            Commit: 1299e2aff9af57fc8a79a6fa09c1676a61cbfa4b

            gerrit Gerrit Updater added a comment - Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/18192/ Subject: LU-7584 tests: create file on single MDS in sanity test 129 Project: fs/lustre-release Branch: master Current Patch Set: Commit: 1299e2aff9af57fc8a79a6fa09c1676a61cbfa4b

            Another instance for FULL - EL7.1 Server/EL7.1 Client - DNE, master, build# 3314
            https://testing.hpdd.intel.com/test_sets/6b7e1dae-cac5-11e5-9609-5254006e85c2

            standan Saurabh Tandan (Inactive) added a comment - Another instance for FULL - EL7.1 Server/EL7.1 Client - DNE, master, build# 3314 https://testing.hpdd.intel.com/test_sets/6b7e1dae-cac5-11e5-9609-5254006e85c2
            bogl Bob Glossman (Inactive) added a comment - another on master: https://testing.hpdd.intel.com/test_sets/be6a1f10-c555-11e5-b0fc-5254006e85c2

            Jian Yu (jian.yu@intel.com) uploaded a new patch: http://review.whamcloud.com/18192
            Subject: LU-7584 tests: create file on single MDS in sanity test 129
            Project: fs/lustre-release
            Branch: master
            Current Patch Set: 1
            Commit: a3518d6fd8e2af08f43c41bb413edee19ee56f64

            gerrit Gerrit Updater added a comment - Jian Yu (jian.yu@intel.com) uploaded a new patch: http://review.whamcloud.com/18192 Subject: LU-7584 tests: create file on single MDS in sanity test 129 Project: fs/lustre-release Branch: master Current Patch Set: 1 Commit: a3518d6fd8e2af08f43c41bb413edee19ee56f64
            yujian Jian Yu added a comment -

            Thank you, Di. Let me create a patch.

            yujian Jian Yu added a comment - Thank you, Di. Let me create a patch.
            di.wang Di Wang added a comment -

            Hmm, I saw it only create 1 more file then check if it pass the limit, which seems not right to me. Because the previous ENOSPC failure might happen on different stripes, i.e. if the new file is created in different stripe, then this check will fail.

            IMHO, probably you can just replace test_mkdir with mkdir and only do single MDS check (of course also removed those STRIPE_COUNT thing), since this test is for checking ldiskfs parameters, this probably makes sense.

            Or

            you need create the new file on the specific stripe by lfs mkdir, instead of using multiop, but then you also need find out which stripe is "FULL" here.

            di.wang Di Wang added a comment - Hmm, I saw it only create 1 more file then check if it pass the limit, which seems not right to me. Because the previous ENOSPC failure might happen on different stripes, i.e. if the new file is created in different stripe, then this check will fail. IMHO, probably you can just replace test_mkdir with mkdir and only do single MDS check (of course also removed those STRIPE_COUNT thing), since this test is for checking ldiskfs parameters, this probably makes sense. Or you need create the new file on the specific stripe by lfs mkdir, instead of using multiop, but then you also need find out which stripe is "FULL" here.

            http://review.whamcloud.com/#/c/17874 already adds the missing patch to the el7.2 patch series, but the failure still happens anyway.

            bogl Bob Glossman (Inactive) added a comment - http://review.whamcloud.com/#/c/17874 already adds the missing patch to the el7.2 patch series, but the failure still happens anyway.
            yujian Jian Yu added a comment -

            The above patch just added warning messages while directory size growing but didn't resolve the issue in this ticket. All of the failure instances occurred under DNE configuration.

            Di, do you think the following comparison in the current sanity test_129() is correct under DNE configuration?

                                    I=$(stat -c%s "$DIR/$tdir")
            
                                    if [ $(lustre_version_code $SINGLEMDS) -lt \
                                                    $(version_code 2.4.51) ]
                                    then
                                            [[ $I -eq $MAX ]] && return 0
                                    else
                                            [[ $I -gt $MAX ]] && return 0
                                    fi
                                    error_exit "current dir size $I, previous limit $MAX"
            
            yujian Jian Yu added a comment - The above patch just added warning messages while directory size growing but didn't resolve the issue in this ticket. All of the failure instances occurred under DNE configuration. Di, do you think the following comparison in the current sanity test_129() is correct under DNE configuration? I=$(stat -c%s "$DIR/$tdir" ) if [ $(lustre_version_code $SINGLEMDS) -lt \ $(version_code 2.4.51) ] then [[ $I -eq $MAX ]] && return 0 else [[ $I -gt $MAX ]] && return 0 fi error_exit "current dir size $I, previous limit $MAX"

            Jian Yu (jian.yu@intel.com) uploaded a new patch: http://review.whamcloud.com/18169
            Subject: LU-7584 ldiskfs: add dir htree growing warning patch
            Project: fs/lustre-release
            Branch: master
            Current Patch Set: 1
            Commit: 7f7a1eb405f17c974fe0d2747c0b871629aaf25c

            gerrit Gerrit Updater added a comment - Jian Yu (jian.yu@intel.com) uploaded a new patch: http://review.whamcloud.com/18169 Subject: LU-7584 ldiskfs: add dir htree growing warning patch Project: fs/lustre-release Branch: master Current Patch Set: 1 Commit: 7f7a1eb405f17c974fe0d2747c0b871629aaf25c
            yujian Jian Yu added a comment -

            As per http://review.whamcloud.com/15548, ext4-give-warning-with-dir-htree-growing.patch is also needed in the new ldiskfs-3.10-rhel7.2.series and ldiskfs-3.12-sles12.series. I'm creating the patch.

            yujian Jian Yu added a comment - As per http://review.whamcloud.com/15548 , ext4-give-warning-with-dir-htree-growing.patch is also needed in the new ldiskfs-3.10-rhel7.2.series and ldiskfs-3.12-sles12.series. I'm creating the patch.

            People

              yujian Jian Yu
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: