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

conf-sanity test_101a: hung in recovery

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • None
    • None
    • 3
    • 9223372036854775807

      This issue was created by maloo for alexey lyashkov <alexey.lyashkov@hpe.com>

      This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/f1bc6aa0-d478-40da-bdfb-a4ffbab58846

      test_101a failed with the following error:

      Timeout occurred after 471 minutes, last suite running was conf-sanity
      

      Test session details:
      clients: https://build.whamcloud.com/job/lustre-reviews/116839 - 5.14.0-503.40.1.el9_5.x86_64
      servers: https://build.whamcloud.com/job/lustre-reviews/116839 - 5.14.0-503.40.1_lustre.el9.x86_64

      <<Please provide additional information about the failure here>>

      Due stack traces analyse - client stick in ldlm enqueue to wait a file creation, but MDT is idle and don't process an rpc. I might be problem with large AT_MAX or some other network issues.

      VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
      conf-sanity test_101a - Timeout occurred after 471 minutes, last suite running was conf-sanity

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

              Created:
              Updated: