[LU-13459] sanity-lfsck test_10: lfsck does not complete before 32s timeout Created: 16/Apr/20  Updated: 16/Apr/20

Status: Open
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Maloo Assignee: WC Triage
Resolution: Unresolved Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for Olaf Faaland <faaland1@llnl.gov>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/ab082c06-d3f6-4bdf-8275-f5a14b216edf

test_10 failed with the following error:

(16) unexpected status

Occurred testing a patch based on b2_12. This was the only failure in a standard test run (ie no Test-Parameters specified). There were 2 clients, 4 MDTs, and 8 OSTs. 5 VMs total.

The test has run a "namespace" type lfsck and is waiting for it to finish.
This is done via wait_update_facet() checking the output of get_param -n mdd.${MDT_DEV}.lfsck_namespace for '^status:.*completed".

wait_update_facet() reported "Update not seen after 32s: wanted 'completed' got 'scanning-phase2'"

There are no console log warnings or errors during the test run, on any of the nodes.

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity-lfsck test_10 - (16) unexpected status


Generated at Sat Feb 10 03:01:27 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.