https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-2586 Lustre <p>Seeing as how server side layout lock code invents some way to sidestep this, we really need to implement a "good to have" lock properties alongside of "absolute must subset of lock properties" requested.</p> <p>Obvious first candidate would be inodebit locks with two sets of bits, mandatory and "nice to have".</p> <p>This probably would couple nice with lock conversion too.</p> LU-2586

Need a way to request "good to have" lock bits

Improvement Major Resolved Duplicate WC Triage Oleg Drokin Mon, 7 Jan 2013 20:34:56 +0000 Sat, 16 Sep 2017 08:27:42 +0000 Sat, 16 Sep 2017 08:27:42 +0000 Lustre 2.4.0 Lustre 2.11.0 0 6 <p>Another useful feature for inodebits lock is to provide a reason why a lock is cancelled. By adding this feature, we need to pack one more field in blocking_ast and client may handle it differently </p> <p>What do you mean by "why"?</p> <p>To indicate the reason for the cancellation of the lock - for example, when a layout lock is being cancelled, it'll be useful to tell the clients the reason as the layout lock may be cancelled because of false sharing, or there is real layout change happening.</p> <p>It turned out to be useful also in file unlink case in patch <a href="http://review.whamcloud.com/7942" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/7942</a> where a file is unlinked by one client so MDT revokes namespace lock but other clients have no idea what's happening. If the MDT could transfer this information to the clients, the clients would take the inode out of cache.</p> <p>This is fixed as part of patch <a href="https://review.whamcloud.com/28022" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/28022</a> for the DoM project.</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>LU-9184 ldlm: selective IBITS lock trying here is code to get lock without blocking, e.g. 'try' to get it. It enqueues lock with all wanted bits and get it only when all bits are not conflicting. The new code allows to get as much 'tried' bits as possible. It also doesn't require extra locking attempt for that. Patch intoduces new inodebits field try_bits which contains optinal bits to get if possible without blocking. Those bits are checked along with the required bits and only non-blocked are added to the new IBITS lock. </pre> </div></div> Duplicate LU-9148 Development Rank 1|hzveqn: Rank (Obsolete) 6029