[LU-5667] LBUG in osd_index_try() when creating striped directory with mix ldiskfs/zfs MDTs Created: 25/Sep/14  Updated: 27/Apr/15  Resolved: 27/Apr/15

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

Type: Bug Priority: Blocker
Reporter: Johann Lombardi (Inactive) Assignee: WC Triage
Resolution: Fixed Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 15879

 Description   

setdirstripe -c -1 on the soak cluster triggered the following LBUG:

LustreError: 5339:0:(osd_index.c:1576:osd_index_try()) ASSERTION( dt_object_exists(dt) ) failed: 
LustreError: 5339:0:(osd_index.c:1576:osd_index_try()) LBUG
Pid: 5339, comm: mdt_out03_000

Call Trace:
 [<ffffffffa064a895>] libcfs_debug_dumpstack+0x55/0x80 [libcfs]
 [<ffffffffa064ae97>] lbug_with_loc+0x47/0xb0 [libcfs]
 [<ffffffffa0efc514>] osd_index_try+0x224/0x4c0 [osd_zfs]
 [<ffffffffa07a6f41>] dt_try_as_dir+0x41/0x60 [obdclass]
 [<ffffffffa0a44c38>] out_index_insert+0x468/0x770 [ptlrpc]
 [<ffffffffa07a4ffb>] ? lu_object_put+0x12b/0x330 [obdclass]
 [<ffffffffa0a46cec>] out_handle+0x94c/0xdf0 [ptlrpc]
 [<ffffffffa09d89cc>] ? lustre_msg_get_opc+0x9c/0x110 [ptlrpc]
 [<ffffffffa0a3be5e>] tgt_request_handle+0x71e/0xb10 [ptlrpc]
 [<ffffffffa09eb6c4>] ptlrpc_main+0xe64/0x1990 [ptlrpc]
 [<ffffffff810096f0>] ? __switch_to+0xd0/0x320
 [<ffffffff8152970e>] ? thread_return+0x4e/0x770
 [<ffffffffa09ea860>] ? ptlrpc_main+0x0/0x1990 [ptlrpc]
 [<ffffffff8109abf6>] kthread+0x96/0xa0
 [<ffffffff8100c20a>] child_rip+0xa/0x20
 [<ffffffff8109ab60>] ? kthread+0x0/0xa0
 [<ffffffff8100c200>] ? child_rip+0x0/0x20

We have 2 MDTs, MDT0 used a ldisfks backend while MDT1 uses ZFS. The LBUG happened on the ZFS MDT.



 Comments   
Comment by Johann Lombardi (Inactive) [ 25/Sep/14 ]

Wangdi, is this something known?

Comment by Di Wang [ 25/Sep/14 ]

Hmm, I am not aware of this. Could you please post the lbug dump log here? Thanks

Comment by Johann Lombardi (Inactive) [ 13/Mar/15 ]

Not relevant any more.

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