[LU-5685] (cl_lock.c:1128:cl_use_try()) ASSERTION( result != -38 )

• Status: Closed
• Project: Lustre
• Affects Version/s: Lustre 2.4.3
• Type: Bug
• Priority: Minor
• Reporter: Bruno Travouillon (Inactive)
• Assignee: Jinshan Xiong (Inactive)
• Resolution: Cannot Reproduce
• Labels: p4b

Environment

RHEL6 w/ patched kernel 2.6.32-431.11.2.el6
Lustre 2.4.3 + bullpatches

• Severity: 3

Description

We hit the following LBUG twice on two Lustre clients:

LustreError: 116840:0:(lcommon_cl.c:1201:cl_file_inode_init()) Failure to initialize cl object [0x22b09fa54:0x1550:0x0]: -16
LustreError: 116850:0:(cl_lock.c:1128:cl_use_try()) ASSERTION( result != -38 ) failed:
LustreError: 116850:0:(cl_lock.c:1128:cl_use_try()) LBUG
Pid: 116850, comm: XXXXXXXXXXXXXXX

Call Trace:
 [<ffffffffa042c895>] libcfs_debug_dumpstack+0x55/0x80 [libcfs]
 [<ffffffffa042ce97>] lbug_with_loc+0x47/0xb0 [libcfs]
 [<ffffffffa05a7fa6>] cl_use_try+0x2a6/0x2e0 [obdclass]
 [<ffffffffa05a813d>] cl_enqueue_try+0x15d/0x300 [obdclass]
 [<ffffffffa05a8fff>] cl_enqueue_locked+0x6f/0x1f0 [obdclass]
 [<ffffffffa05a9c6e>] cl_lock_request+0x7e/0x270 [obdclass]
 [<ffffffffa0b61f00>] cl_glimpse_lock+0x180/0x490 [lustre]
 [<ffffffffa0b62775>] cl_glimpse_size0+0x1a5/0x1d0 [lustre]
 [<ffffffffa0b15528>] ll_inode_revalidate_it+0x198/0x1c0 [lustre]
 [<ffffffff81197036>] ? final_putname+0x26/0x50
 [<ffffffffa0b15599>] ll_getattr_it+0x49/0x170 [lustre]
 [<ffffffffa0b156f7>] ll_getattr+0x37/0x40 [lustre]
 [<ffffffff81227b23>] ? security_inode_getattr+0x23/0x30
 [<ffffffff8118f001>] vfs_getattr+0x51/0x80
 [<ffffffff8118f094>] vfs_fstatat+0x64/0xa0
 [<ffffffff811bd788>] ? user_statfs+0x38/0xb0
 [<ffffffff8118f13e>] vfs_lstat+0x1e/0x20
 [<ffffffff8118f164>] sys_newlstat+0x24/0x50
 [<ffffffff810686d5>] ? sys_sched_yield+0x55/0x60
 [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b

Both time, it was the same user with two version of a code. We were not able to reproduce since.

Issue Links

• is related to: LU-5062 LBUG: osc_req_attr_set

Comments

[Peter Jones]

Jinshan is looking into this

[Jinshan Xiong (Inactive)]

This should be a reproduction of LU-5062. Now that this occurred at b2_4 so I will leave this ticket open and back port the patch.

[Jinshan Xiong (Inactive)]

patch is here: http://review.whamcloud.com/12137

[Bruno Travouillon (Inactive)]

Thanks Jinshan.

Are you aware of a backport to b2_5? We should upgrade soon to this maintenance release.

[Peter Jones]

b2_5 port http://review.whamcloud.com/#/c/12139/

[Bruno Travouillon (Inactive)]

We hit this bug in 2.5.3 as well.

[Peter Jones]

Bruno

Were you carrying the LU-5062 patch against 2.5.3 when you hit this issue?

Peter

[Bruno Travouillon (Inactive)]

If you mean b2_5 port http://review.whamcloud.com/#/c/12139/ , no, we don't have this patch in our build. Seems it need some more reviewers.

[Bruno Travouillon (Inactive)]

Peter,

Can we safely use the b2_5 port on top of 2.5.3?

[Peter Jones]

Yes that is fine

[Jinshan Xiong (Inactive)]

This is about old cl_lock that doesn't exist any more