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-13096 Lustre <p>it seems to print incorrect used_mb size in max_cached_mb on large memory client.<br/> that client has 24TB memory and it has 12TB for max_cached_mb by default, but max_cached_mb says most of cache is "used_mb".</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>sdf2{root}1014: free total used free shared buff/cache available Mem: 24965051716 139544736 24824112084 39772 1394896 24818988328 Swap: 8388604 0 8388604 sdf2{root}1015: lctl get_param llite.*.max_cached_mb llite.lustre-ffff96631b3d6800.max_cached_mb= users: 16 max_cached_mb: 12189966 used_mb: 12157198 unused_mb: 32768 reclaim_count: 0 'Drop cache' doesn't help niether. sdf2{root}1016: echo 3 &gt; /proc/sys/vm/drop_caches sdf2{root}1017: lctl get_param llite.*.max_cached_mb llite.lustre-ffff96631b3d6800.max_cached_mb= users: 16 max_cached_mb: 12189966 used_mb: 12157198 unused_mb: 32768 reclaim_count: 0</pre> </div></div> LU-13096

incorrect used_mb in max_cached_mb

Bug Minor Resolved Fixed Emoly Liu Emoly Liu Fri, 20 Dec 2019 14:18:16 +0000 Sat, 13 Jun 2020 10:23:24 +0000 Tue, 17 Mar 2020 18:01:53 +0000 Lustre 2.14.0 0 7 <p><del>Emoly Liu (emoly@whamcloud.com) uploaded a new patch:</del> <a href="https://review.whamcloud.com/37080" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/37080</a><br/> <del>Subject: <a href="https://jira.whamcloud.com/browse/LU-13096" title="incorrect used_mb in max_cached_mb" class="issue-link" data-issue-key="LU-13096"><del>LU-13096</del></a> client: fix incorrect used_mb in max_cached_mb</del><br/> <del>Project: fs/lustre-release</del><br/> <del>Branch: master</del><br/> <del>Current Patch Set: 1</del><br/> <del>Commit: f9e0b9f65b3f529e3dacaab53ae12f738ed11945</del></p> <p>I want to make sure I understand things correctly.  This patch doesn't actually attempt to fix the problem does it?  On a 64 bit platform as far as I can tell an atomic_long_t is an atomic64_t.  Today I was able to confirm that the patch had no effect for us.</p> <p>Wang Shilong (wshilong@ddn.com) uploaded a new patch: <a href="https://review.whamcloud.com/37707" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/37707</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-13096" title="incorrect used_mb in max_cached_mb" class="issue-link" data-issue-key="LU-13096"><del>LU-13096</del></a> llite: fix potential overflow in ll_max_cached_mb_seq_write()<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 83576aeab760887fc8fd58290fb22d59641705ce</p> <p><del>Wang Shilong (wshilong@ddn.com) uploaded a new patch:</del> <a href="https://review.whamcloud.com/37708" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/37708</a><br/> <del>Subject: <a href="https://jira.whamcloud.com/browse/LU-13096" title="incorrect used_mb in max_cached_mb" class="issue-link" data-issue-key="LU-13096"><del>LU-13096</del></a> llite: limit default max lru pages</del><br/> <del>Project: fs/lustre-release</del><br/> <del>Branch: master</del><br/> <del>Current Patch Set: 1</del><br/> <del>Commit: 48202d2aad10f75f8d6df3f10400ab4c6c23a85e</del></p> <p>Wang Shilong (wshilong@ddn.com) uploaded a new patch: <a href="https://review.whamcloud.com/37710" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/37710</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-13096" title="incorrect used_mb in max_cached_mb" class="issue-link" data-issue-key="LU-13096"><del>LU-13096</del></a> llite: serialize max_cached_mb write operation<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 0247c40f5ff6884856575199bb74a1e9e815afe0</p> <p>Oleg Drokin (green@whamcloud.com) merged in patch <a href="https://review.whamcloud.com/37707/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/37707/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-13096" title="incorrect used_mb in max_cached_mb" class="issue-link" data-issue-key="LU-13096"><del>LU-13096</del></a> llite: fix potential overflow in ll_max_cached_mb_seq_write()<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: a7d0e91ea687564d3d5be0eb96bd5b6a260e665b</p> <p>Oleg Drokin (green@whamcloud.com) merged in patch <a href="https://review.whamcloud.com/37710/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/37710/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-13096" title="incorrect used_mb in max_cached_mb" class="issue-link" data-issue-key="LU-13096"><del>LU-13096</del></a> llite: serialize max_cached_mb write operation<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: e4d63c854d774792f8a77b8d1e575ccc2d8c3c8b</p> <p>Landed for 2.14</p> Duplicate Related Development Rank 1|i00rbz: Rank (Obsolete) 9223372036854775807 Severity