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

sanityn test_78: Expected set_param to return 0 or EAGAIN

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: Lustre 2.8.0
    • Fix Version/s: Lustre 2.8.0
    • Labels:
      None
    • Severity:
      3
    • Rank (Obsolete):
      9223372036854775807

      Description

      This issue was created by maloo for Andreas Dilger <andreas.dilger@intel.com>

      This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/7cec4ac6-4f04-11e5-bc53-5254006e85c2.

      The sub-test test_78 failed with the following error:

      CMD: shadow-21vm3 lctl set_param ost.OSS.ost_io.nrs_policies=orr
      CMD: shadow-21vm3 lctl set_param ost.OSS.*.nrs_orr_quantum=1
      shadow-21vm3: error: set_param: setting ost.OSS.ost_io.nrs_orr_quantum=1: No such device
      ost.OSS.ost_io.nrs_orr_quantum=1
       sanityn test_78: @@@@@@ FAIL: Expected set_param to return 0 or EAGAIN
      

      This may relate to the recently landed patch:
      http://review.whamcloud.com/15104 "LU-6673 ptlrpc: Forbid too early NRS policy tunings"

      This just started on Aug 30, and all patches failing so far are based on either:
      LU-6667 llite: improve ll_getname
      LU-6903 lov: call lov_object_find_cbdata() inside lock

      Info required for matching: sanityn 78

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                hdoreau Henri Doreau (Inactive)
                Reporter:
                maloo Maloo
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: