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-16062 Lustre <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>531.159590] LustreError: 10802:0:(ldlm_lockd.c:256:expired_lock_main()) ### lock callback timer expired after 99s: evicting client at 192.168.2.7@tcp ns: mdt-lustre-MDT0002_UUID lock: ffff880967ce0480/0xd2e918f816df7d21 lrc: 3/0,0 mode: CR/CR res: [0x280000407:0x150:0x0].0x0 bits 0x9/0x0 rrc: 3 type: IBT flags: 0x60200400000020 nid: 192.168.2.7@tcp remote: 0x794bcb111018717d expref: 49 pid: 12233 timeout: 530 lvb_type: 0 </pre> </div></div> <p>while client timeout is <br/> pb_timeout = 152,</p> <p>So, if the reply was lost the client doesn't have time to resend.</p> LU-16062

Different client and server timeouts during lock enqueue with BL AST set

Bug Minor Resolved Fixed Vitaly Fertman Vitaly Fertman Sun, 31 Jul 2022 20:02:20 +0000 Tue, 11 Oct 2022 07:48:00 +0000 Mon, 12 Sep 2022 15:28:26 +0000 Lustre 2.16.0 0 5 <p>"Vitaly Fertman &lt;vitaly.fertman@hpe.com&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/48094" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/48094</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-16062" title="Different client and server timeouts during lock enqueue with BL AST set" class="issue-link" data-issue-key="LU-16062"><del>LU-16062</del></a> ldlm: improve bl_timeout for prolong<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: b0352aa23c01edf6ca2755875a8b914e10e0051a</p> <p>Landed for 2.16</p> Related Development Rank 1|i02vvb: Rank (Obsolete) 9223372036854775807 Severity