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

sanity-quota test_63: Timeout occurred, last suite running was sanity-quota

XMLWordPrintable

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

      sanity-quota times out with test_63 as the last test running: "Timeout occurred after N minutes, last suite running was sanity-quota". No ticket links this signature.

      Seen 227 times in 60 days on test_63: 212 on lustre-master and master-next (about 14% of full-part-2 suite runs) plus the b2_16-client interop custom group of reviews 67700 and 69011.

      Example: https://testing.whamcloud.com/test_sets/5997d7d4-cbb5-486a-8fd6-7172047afff1 (change 69011 ps6). Suite started 17:56, test_63 started 19:38 and was still running at the 197 minute timeout. The client had a dd stuck in folio_wait_writeback under ll_fsync, and the suite log shows OST and MDT connection losses and evictions earlier in the run. The same session also fails test_0 with SLOW IO (406 kB/s, quota disabled).

      Not the same as LU-17077 (test_63 "write failed, expect succeed").

      Raised by Patch Watcher run pw-engineer-69011-ps6-ea8c8a8edd12 on https://review.whamcloud.com/69011

      VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
      sanity-quota test_63 - Timeout occurred after 197 minutes, last suite running was sanity-quota

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

              Created:
              Updated: