[LU-13825] sanity-lfsck test_18b: (2) MDS4 is not the expected 'completed'

• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Affects Version/s: Lustre 2.12.6
• Severity: 3
• Assignee: WC Triage
• Reporter: Maloo

Description

This issue was created by maloo for Olaf Faaland <[e-mail]>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/8f623a2c-dce5-440b-a641-3b30e4b1b1e1

test_18b failed with the following error:

(2) MDS4 is not the expected 'completed'

Leading up to that in the logs:

Trigger layout LFSCK on all devices to find out orphan OST-object
CMD: trevis-25vm4 /usr/sbin/lctl lfsck_start -M lustre-MDT0000 -t layout -r -o
Started LFSCK on the device lustre-MDT0000: scrub layout

followed by

Update not seen after 120s: wanted 'completed' got 'scanning-phase2'
 sanity-lfsck test_18b: @@@@@@ FAIL: (2) MDS4 is not the expected 'completed' 

Bash trace dump is:

  Trace dump:
  = /usr/lib64/lustre/tests/test-framework.sh:5907:error()
  = /usr/lib64/lustre/tests/sanity-lfsck.sh:2197:test_18b()
  = /usr/lib64/lustre/tests/test-framework.sh:6210:run_one()
  = /usr/lib64/lustre/tests/test-framework.sh:6259:run_one_logged()
  = /usr/lib64/lustre/tests/test-framework.sh:6099:run_test()
  = /usr/lib64/lustre/tests/sanity-lfsck.sh:2260:main()

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity-lfsck test_18b - (2) MDS4 is not the expected 'completed'