[LU-15324] sanity test_56xb timeout

• Type: Bug
• Resolution: Duplicate
• Priority: Minor
• Severity: 3
• Assignee: WC Triage
• Reporter: Maloo

Description

This issue was created by maloo for S Buisson <[e-mail]>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/968beb60-7f06-45e5-ac42-bfbb9bed9dde

test_56xb failed with the following error:

Timeout occurred after 259 mins, last suite running was sanity

This timeout is due to a service thread hung on the MDS:

[13521.648380] Lustre: mdt00_004: service thread pid 21846 was inactive for 42.205 seconds. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:
[13521.655315] Pid: 21846, comm: mdt00_004 4.18.0-240.22.1.el8_lustre.x86_64 #1 SMP Mon Nov 8 22:25:55 UTC 2021
[13521.656859] Call Trace TBD:
[13521.657864] [<0>] ldlm_completion_ast+0x7ac/0x900 [ptlrpc]
[13521.658785] [<0>] ldlm_cli_enqueue_local+0x307/0x860 [ptlrpc]
[13521.659848] [<0>] mdt_object_local_lock+0x446/0xb30 [mdt]
[13521.660725] [<0>] mdt_object_lock_internal+0x18d/0x4a0 [mdt]
[13521.661629] [<0>] mdt_getattr_name_lock+0x1873/0x2250 [mdt]
[13521.662528] [<0>] mdt_intent_getattr+0x27a/0x450 [mdt]
[13521.663363] [<0>] mdt_intent_opc+0x12c/0xbf0 [mdt]
[13521.664145] [<0>] mdt_intent_policy+0x207/0x3a0 [mdt]
[13521.664983] [<0>] ldlm_lock_enqueue+0x4e4/0xa80 [ptlrpc]
[13521.665876] [<0>] ldlm_handle_enqueue0+0x634/0x1760 [ptlrpc]
[13521.666827] [<0>] tgt_enqueue+0xa4/0x210 [ptlrpc]
[13521.667609] [<0>] tgt_request_handle+0xc93/0x1a00 [ptlrpc]
[13521.668518] [<0>] ptlrpc_server_handle_request+0x323/0xbd0 [ptlrpc]
[13521.669544] [<0>] ptlrpc_main+0xc06/0x1550 [ptlrpc]
[13521.670353] [<0>] kthread+0x112/0x130
[13521.670953] [<0>] ret_from_fork+0x35/0x40

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity test_56xb - Timeout occurred after 259 mins, last suite running was sanity

Issue Links

• duplicates: LU-15320 sanity-quota: test_59 TIMEOUT