[LU-4524] ldlm_handle_enqueue0 incorrectly interprets ldlm_lock_create's NULL return value Created: 21/Jan/14  Updated: 16/Oct/17  Resolved: 16/Jun/14

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.6.0, Lustre 2.4.2, Lustre 2.5.1
Fix Version/s: Lustre 2.6.0

Type: Improvement Priority: Major
Reporter: Shuichi Ihara (Inactive) Assignee: Emoly Liu
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Related
is related to LU-4970 Test failure sanity-lfsck test_14: ls... Resolved
is related to LU-4230 Test failure on test suite replay-ost... Resolved
Rank (Obsolete): 12373

 Description   

As described by John in LU-4034, ldlm_handle_enqueue0 assumes that NULL values from ldlm_lock_create are due to memory errors. In reality, there are other causes, such as ENOENT. The error reporting should be fixed as it causes confusion for sysadmins, and can waste time.

Logs from LU-4034:

Oct 1 16:20:11 zeus kernel: LustreError: 11-0: scratch-OST0013-osc-ffff8804925f1400: Communicating with 172.16.126.4@tcp, operation ldlm_enqueue failed with -12.
Oct 1 16:20:11 zeus kernel: LustreError: 23207:0:(cl_lock.c:1420:cl_unuse_try()) result = -12, this is unlikely!
Oct 1 16:20:11 scratch02 kernel: LustreError: 4630:0:(ldlm_resource.c:1165:ldlm_resource_get()) scratch-OST0013: lvbo_init failed for resource 0x40d9dcf:0x0: rc = -2


 Comments   
Comment by Peter Jones [ 22/Jan/14 ]

Emoly

Could you please help with this one?

thanks

Peter

Comment by Emoly Liu [ 27/Jan/14 ]

The patch is at http://review.whamcloud.com/9004 .

Comment by Emoly Liu [ 16/Jun/14 ]

The patch landed to 2.6.

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