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

1.8<->2.1 interop: sanity test_132: FAIL: some glimpse RPC is expected

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.4.0, Lustre 2.1.5
    • Lustre 2.0.0, Lustre 2.1.2, Lustre 2.1.3, Lustre 1.8.8, Lustre 1.8.6
    • None
    • 3
    • 23,339
    • 4234

    Description

      After the upgrading, sanity test 132 failed on Lustre 2.0.66.0 as follows:

      == sanity test 132: som avoids glimpse rpc == 03:17:56 (1312885076)
      ====> SOM is disabled, 0 glimpse RPC occured
       sanity test_132: @@@@@@ FAIL: some glimpse RPC is expected 
      

      Please refer to the Maloo report for more logs: https://maloo.whamcloud.com/test_sets/a570d34e-c278-11e0-8bdf-52540025f9af

      This is an known issue: bug 23339.

      Attachments

        Issue Links

          Activity

            [LU-582] 1.8<->2.1 interop: sanity test_132: FAIL: some glimpse RPC is expected

            I've been using http://review.whamcloud.com/#change,3693 for
            several months, and recommend it for b2_1.

            schamp Stephen Champion added a comment - I've been using http://review.whamcloud.com/#change,3693 for several months, and recommend it for b2_1.

            I saw this problem between 2.1.3 server and 2.3.0 client. Let me know if you want the test_logs.

            jaylan Jay Lan (Inactive) added a comment - I saw this problem between 2.1.3 server and 2.3.0 client. Let me know if you want the test_logs.

            the patch has been updated

            hongchao.zhang Hongchao Zhang added a comment - the patch has been updated

            there is a bug in get_ost_param

            get_ost_param() {
            local token=$1
            local gl_sum=0
            for node in $(osts_nodes); do
            gl=$(do_node $node "$LCTL get_param -n ost.OSS.ost.stats" | awk '/'$token'/

            {print $2}

            ' | head -n 1)
            [ x$gl = x"" ] && gl=0
            gl_sum=$((gl_sum + gl))
            done
            echo $gl <--- here should be "echo $gl_sum"!
            }

            previous, there is only one OSS in autotest, then the problem is hidden, but in upgrade test, there are 2 OSS,
            then the issue shows up. the updated patch will be attached soon!

            hongchao.zhang Hongchao Zhang added a comment - there is a bug in get_ost_param get_ost_param() { local token=$1 local gl_sum=0 for node in $(osts_nodes); do gl=$(do_node $node "$LCTL get_param -n ost.OSS.ost.stats" | awk '/'$token'/ {print $2} ' | head -n 1) [ x$gl = x"" ] && gl=0 gl_sum=$((gl_sum + gl)) done echo $gl <--- here should be "echo $gl_sum"! } previous, there is only one OSS in autotest, then the problem is hidden, but in upgrade test, there are 2 OSS, then the issue shows up. the updated patch will be attached soon!
            yujian Jian Yu added a comment -

            the debug patch is tracked at http://review.whamcloud.com/#change,3692

            The real patch is in http://review.whamcloud.com/#change,3693. Testing is ongoing.

            yujian Jian Yu added a comment - the debug patch is tracked at http://review.whamcloud.com/#change,3692 The real patch is in http://review.whamcloud.com/#change,3693 . Testing is ongoing.

            Yujian help to reproduce the bug after upgrading Lustre, and the ldlm_glimpse_enqueue is indeed increased.

            the debug patch is tracked at http://review.whamcloud.com/#change,3692

            Hi Yujian, could you please help to test with the debug patch? thanks!!

            hongchao.zhang Hongchao Zhang added a comment - Yujian help to reproduce the bug after upgrading Lustre, and the ldlm_glimpse_enqueue is indeed increased. the debug patch is tracked at http://review.whamcloud.com/#change,3692 Hi Yujian, could you please help to test with the debug patch? thanks!!

            People

              hongchao.zhang Hongchao Zhang
              yujian Jian Yu
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: