[LU-6185] EL7 client sanity-lfsck test_5: lfsck in D state Created: 30/Jan/15  Updated: 31/Jan/15  Resolved: 31/Jan/15

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.7.0
Fix Version/s: None

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

server: lustre-mater build #2830 RHEL6
client: EL7


Severity: 3
Rank (Obsolete): 17306

 Description   

This issue was created by maloo for sarah <sarah@whamcloud.com>

This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/c79c2c5a-a494-11e4-a1ef-5254006e85c2.

The sub-test test_5 failed with the following error:

test failed to respond and timed out

MDS

lfsck         D 0000000000000001     0 26785      2 0x00000080
05:31:30: ffff880055ae3c30 0000000000000046 0000000000000000 ffff880056b3c070
05:31:30: ffff880056b3c070 ffff880069b7c000 ffff880055ae3c30 ffffffffa05fbd49
05:31:30: ffff88005a256638 ffff880055ae3fd8 000000000000fbc8 ffff88005a256638
05:31:30:Call Trace:
05:31:30: [<ffffffffa05fbd49>] ? lu_object_find_try+0x99/0x2b0 [obdclass]
05:31:30: [<ffffffffa05fbf9d>] lu_object_find_at+0x3d/0xe0 [obdclass]
05:31:30: [<ffffffff81061d00>] ? default_wake_function+0x0/0x20
05:31:30: [<ffffffffa05fc07f>] lu_object_find_slice+0x1f/0x80 [obdclass]
05:31:30: [<ffffffffa0e347d8>] lfsck_master_oit_engine+0x5e8/0x1f30 [lfsck]
05:31:30: [<ffffffffa0e36bf6>] lfsck_master_engine+0xad6/0x13c0 [lfsck]
05:31:31: [<ffffffff81061d00>] ? default_wake_function+0x0/0x20
05:31:31: [<ffffffffa0e36120>] ? lfsck_master_engine+0x0/0x13c0 [lfsck]
05:31:31: [<ffffffff8109abf6>] kthread+0x96/0xa0
05:31:31: [<ffffffff8100c20a>] child_rip+0xa/0x20
05:31:31: [<ffffffff8109ab60>] ? kthread+0x0/0xa0
05:31:31: [<ffffffff8100c200>] ? child_rip+0x0/0x20
05:31:31:INFO: task mdt00_002:26417 blocked for more than 120 seconds.
05:31:31:      Not tainted 2.6.32-431.29.2.el6_lustre.gbb6dbca.x86_64 #1
05:31:31:"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
05:31:31:mdt00_002     D 0000000000000001     0 26417      2 0x00000080
05:31:31: ffff880079467940 0000000000000046 0000000000000000 ffff880079d4cb00
05:31:31: ffff880079d4cb00 ffff880069b7c000 ffff880079467940 ffffffffa05fbd49
05:31:31: ffff88007bb07098 ffff880079467fd8 000000000000fbc8 ffff88007bb07098
05:31:31:Call Trace:
05:31:31: [<ffffffffa05fbd49>] ? lu_object_find_try+0x99/0x2b0 [obdclass]
05:31:31: [<ffffffffa05fbf9d>] lu_object_find_at+0x3d/0xe0 [obdclass]
05:31:31: [<ffffffffa0fd5755>] ? lod_index_lookup+0x25/0x30 [lod]
05:31:31: [<ffffffff81061d00>] ? default_wake_function+0x0/0x20
05:31:31: [<ffffffffa05fc056>] lu_object_find+0x16/0x20 [obdclass]
05:31:31: [<ffffffffa0ee5056>] mdt_object_find+0x56/0x170 [mdt]
05:31:31: [<ffffffffa0f1c2f7>] mdt_reint_open+0x1527/0x2c70 [mdt]
05:31:31: [<ffffffffa04ab82c>] ? upcall_cache_get_entry+0x29c/0x880 [libcfs]
05:31:31: [<ffffffffa0618ca0>] ? lu_ucred+0x20/0x30 [obdclass]
05:31:31: [<ffffffffa0f0403d>] mdt_reint_rec+0x5d/0x200 [mdt]
05:31:31: [<ffffffffa0ee823b>] mdt_reint_internal+0x4cb/0x7a0 [mdt]
05:31:31: [<ffffffffa0ee8706>] mdt_intent_reint+0x1f6/0x430 [mdt]
05:31:31: [<ffffffffa0ee6cf4>] mdt_intent_policy+0x494/0xce0 [mdt]
05:31:31: [<ffffffffa07d04f9>] ldlm_lock_enqueue+0x129/0x9d0 [ptlrpc]
05:31:31: [<ffffffffa07fc4bb>] ldlm_handle_enqueue0+0x51b/0x13f0 [ptlrpc]
05:31:31: [<ffffffffa087d1b2>] tgt_enqueue+0x62/0x1d0 [ptlrpc]
05:31:31: [<ffffffffa087dd9e>] tgt_request_handle+0x8be/0x1000 [ptlrpc]
05:31:31: [<ffffffffa082d891>] ptlrpc_main+0xe41/0x1960 [ptlrpc]
05:31:31: [<ffffffffa082ca50>] ? ptlrpc_main+0x0/0x1960 [ptlrpc]
05:31:31: [<ffffffff8109abf6>] kthread+0x96/0xa0
05:31:31: [<ffffffff8100c20a>] child_rip+0xa/0x20
05:31:31: [<ffffffff8109ab60>] ? kthread+0x0/0xa0
05:31:31: [<ffffffff8100c200>] ? child_rip+0x0/0x20

Info required for matching: sanity-lfsck 5



 Comments   
Comment by nasf (Inactive) [ 31/Jan/15 ]

It is another failure instance of LU-6147 because of the LFSCK was blocked by an object to be purged.

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