[LU-12379] write openlock conflicts needlessly with other operations Created: 04/Jun/19  Updated: 04/Jun/19

Status: Open
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.13.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Oleg Drokin Assignee: WC Triage
Resolution: Unresolved Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

Looks like all the careful logic we had in 1.x releases where all read operations were getting CR locks was lost in 2.x conversion and now whenever we get a CW lock for WRITE openhandle caching, subsequent stats and other such operations would cancel it quickly negating the benefit.

Need to convert most of the locks back to CR mode I guess.



 Comments   
Comment by Gerrit Updater [ 04/Jun/19 ]

Oleg Drokin (green@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/35053
Subject: LU-12379 mdt: getattr_name_lock to get CR lock on a child
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 24a6b1a09246eab364540293d158ccd7e21b23ce

Generated at Sat Feb 10 02:52:04 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.