[LU-5632] ldlm_lock_addref()) ASSERTION( lock != ((void *)0) )

• Type: Bug
• Resolution: Duplicate
• Priority: Major
• Fix Version/s: Lustre 2.5.0
• Affects Version/s: Lustre 2.4.2
• Environment: Lustre 2.4.2-14chaos (see github.com/chaos/lustre); ZFS OSD
• Severity: 3
• Assignee: Niu Yawei (Inactive)
• Reporter: Christopher Morrone (Inactive)

Description

We had an MDS crash with the following assertion:

ldlm_lock.c:770:ldlm_lock_addref()) ASSERTION( lock != ((void *)0) )

The previous few minutes contained many lock timeouts and some node reconnections.

The backtrace for the mdt_02_049 that hit the assertion was:

ldlm_lock_addref
mdt_reint_open
mdt_reconstruct_open
mdt_reconstruct
mdt_reint_internal
mdt_intent_reint
mdt_intent_policy
ldlm_lock_enqueue
ldlm_handle_enqueue0
mdt_enqueue
mdt_handle_common
mds_regular_handle
ptlrpc_server_handle_request
ptlrpc_main

We were running lustre version 2.4.2-14chaos (see github.com/chaos/lustre).

We cannot provide logs or crash dumps from this system.

Issue Links

• is related to: LU-4584 Lock revocation process fails consistently
• is related to: LU-5525 ASSERTION( new_lock->l_readers + new_lock->l_writers == 0 ) failed