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

sanityn test_34: ldlm_add_waiting_lock()) ASSERTION( (((( lock))->l_flags & (1ULL << 52)) != 0) ) failed

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • None
    • Lustre 2.7.0
    • None
    • 3
    • 16845

    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/3cf1c250-8616-11e4-b909-5254006e85c2.

      The sub-test test_34 failed with the following error on the OST:

      01:33:06:Lustre: DEBUG MARKER: == sanityn test 34: no lock timeout under IO == 08:33:02 (1418805182)
      01:33:06:Lustre: DEBUG MARKER: lctl get_param -n ldlm.namespaces.filter-*.lock_timeouts
      01:33:06:Lustre: DEBUG MARKER: lctl set_param fail_loc=0x512
      01:33:06:Lustre: DEBUG MARKER: lctl set_param fail_loc=0x512
      01:33:06:Lustre: *** cfs_fail_loc=512, val=0***
      01:33:06:LustreError: 11571:0:(fail.c:132:__cfs_fail_timeout_set()) cfs_fail_timeout id 512 sleeping for 4000ms
      01:33:06:Lustre: *** cfs_fail_loc=512, val=0***
      01:33:06:LustreError: 3951:0:(ldlm_lockd.c:406:ldlm_add_waiting_lock()) ASSERTION( (((( lock))->l_flags & (1ULL << 52)) != 0) ) failed: 
      01:33:06:LustreError: 3951:0:(ldlm_lockd.c:406:ldlm_add_waiting_lock()) LBUG
      

      Please provide additional information about the failure here.

      Info required for matching: sanityn 34

      Attachments

        Issue Links

          Activity

            People

              wc-triage WC Triage
              maloo Maloo
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: