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-11185 Lustre <p>Regression introduced by 4335d232c3e6fa144d0a2d5e49264761e91b38c7.<br/> It takes additional cld reference to the lock, but lock forget to cancel<br/> during normal shutdown. So this lock holds cld on the list for a long time.<br/> And any config modification needs to cancel each lock separately.</p> <p>Additional bug exist, when lock is obtained but don't processed and marked as lost lock, so two locks objects refers to the single cld instance.</p> LU-11185

MGC lock leak

Bug Minor Resolved Fixed Alexey Lyashkov Alexey Lyashkov Fri, 27 Jul 2018 04:04:55 +0000 Mon, 2 Nov 2020 20:39:53 +0000 Sat, 14 Dec 2019 13:49:05 +0000 Lustre 2.11.0 Lustre 2.12.0 Lustre 2.14.0 0 4 <p>easy reproduce with <br/> <span class="error">&#91;root@rhel7-1 tmp&#93;</span># while [ 1 ]; do umount /mnt/lustre; mount -t lustre -o user_xattr,flock rhel7-1@tcp:/lustre /mnt/lustre; sleep 5; done</p> <p>and dump an MGS namespace to the log.</p> <p>Alexey Lyashkov (c17817@cray.com) uploaded a new patch: <a href="https://review.whamcloud.com/32890" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/32890</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-11185" title="MGC lock leak" class="issue-link" data-issue-key="LU-11185"><del>LU-11185</del></a> mgc: config lock leak<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: cf31de844d11b24ffd71c4d6f23dd63d00bbfc15</p> <p>I don't see commit hash 4335d232c3e6fa144d in our tree. Could you please provide the summary line for this patch.</p> <p>commit 4335d232c3e6fa144d0a2d5e49264761e91b38c7<br/> Author: Jinshan Xiong &lt;jay@whamcloud.com&gt;<br/> Date: Mon Aug 8 19:39:22 2011 -0700</p> <p> <a href="https://jira.whamcloud.com/browse/LU-580" title="update mgc llog process code" class="issue-link" data-issue-key="LU-580"><del>LU-580</del></a>: update mgc llog process code</p> <p> This patch does the following work:<br/> 1. fix a bug about setting mgc lock callback data;<br/> 2. define log instance types;<br/> 3. simplify and cleanup mgc_requeue_thread code</p> <p> Signed-off-by: Jinshan Xiong &lt;jay@whamcloud.com&gt;<br/> Change-Id: Ic8d25eda9f0a7884b4a8cbeccc89c1e66c19f0ff<br/> Reviewed-on: <a href="http://review.whamcloud.com/1198" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/1198</a><br/> Tested-by: Hudson<br/> Tested-by: Maloo &lt;whamcloud.maloo@gmail.com&gt;</p> <p>Is this in some other branch? I still can't find that commit hash, but that patch is very old - 2011, so it should be in every release available today. The commit hash on master for that patch is 5538eee216a194d47ae67fbcff80bfbcd95f3d69. </p> <p>Oleg Drokin (green@whamcloud.com) merged in patch <a href="https://review.whamcloud.com/32890/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/32890/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-11185" title="MGC lock leak" class="issue-link" data-issue-key="LU-11185"><del>LU-11185</del></a> mgc: config lock leak<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 0ad54d59777366fba8ee61eaaa27b3060c91782f</p> <p>Landed for 2.14</p> <p>Jian Yu (yujian@whamcloud.com) uploaded a new patch: <a href="https://review.whamcloud.com/40520" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/40520</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-11185" title="MGC lock leak" class="issue-link" data-issue-key="LU-11185"><del>LU-11185</del></a> mgc: config lock leak<br/> Project: fs/lustre-release<br/> Branch: b2_12<br/> Current Patch Set: 1<br/> Commit: 49db8cbeb579a9485b09f679ebadbc2eca13dda8</p> Related LU-580 Development Rank 1|hzzzxj: Rank (Obsolete) 9223372036854775807 Severity