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-7473 Lustre <p>The current limitation of ACL entries is 32, which is not enough for some use cases. The limitation is inherited since Lustre-1.6 (or even earlier verion). Is there any special reason we keep this small limitation? The only reason I can think of, is to prevent space from exhausting before inodes exhausts on MDT. But, still 32 is too small, can we enlarge or even remove the limitation?</p> LU-7473

Enlarge ACL entry limitation

New Feature Critical Resolved Fixed nasf Li Xi Tue, 24 Nov 2015 11:03:53 +0000 Wed, 27 Jan 2021 22:50:40 +0000 Mon, 15 Jan 2018 17:43:31 +0000 Lustre 2.8.0 Lustre 2.10.0 0 6 <p>The reason that there is a limit on the ACLs is that the client needs to preallocate the reply buffer to receive the ACL data from the server, so it cannot be unlimited. The kernel limit in the past was also 32 entries, which the Lustre code also used.</p> <p>It seems it would be possible to increase the ACL limit to 64 (each entry is only 8 bytes). Since the ACL entries are sharing the same space as the LOV layout there is an upper limit on how much space the two of them can use, so this shouldn't make the replies too large.</p> <p>There will be some compatibility issues if this size is increased, if older and newer clients are mixed in the same cluster, and newer clients set a larger ACL that older clients cannot access. Besides this, I don't <em>think</em> there will be any protocol compatibility issues, since the ACL buffer size is described in the request and the reply, and older servers should be able to handle the larger ACL from newer clients.</p> <p>Please ensure any patch for this is tested with both older and newer clients against older and newer servers. It would also be useful to enhance the conf-sanity test_32 cases to include ACLs, if that is not already the case today.</p> <p>Fan Yong (fan.yong@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/19790" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/19790</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-7473" title="Enlarge ACL entry limitation" class="issue-link" data-issue-key="LU-7473"><del>LU-7473</del></a> acl: increase ACL entries limitation<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 3d33ba9e5d402c48bc8b76b9d4427b391ee85f65</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="https://review.whamcloud.com/19790/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/19790/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-7473" title="Enlarge ACL entry limitation" class="issue-link" data-issue-key="LU-7473"><del>LU-7473</del></a> acl: increase ACL entries limitation<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 64b2fad22a4eb4727315709e014d8f74c5a7f289</p> <p>Landed for 2,10</p> <p>Fan Yong (fan.yong@intel.com) uploaded a new patch: <a href="https://review.whamcloud.com/28116" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/28116</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-7473" title="Enlarge ACL entry limitation" class="issue-link" data-issue-key="LU-7473"><del>LU-7473</del></a> acl: prepare small buffer for ACL in RPC reply<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 971dbecce884acb07baccc175ea1e26336fff11c</p> <p>Reopen to track landing of last patch.</p> <p>The patch <a href="https://review.whamcloud.com/28116" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/28116</a> will be landed via <a href="https://jira.whamcloud.com/browse/LU-10513" title="Prepare small buffer for ACL RPC reply" class="issue-link" data-issue-key="LU-10513"><del>LU-10513</del></a>.</p> <p>Reopen to remove 2.11 fix version. </p> Related LU-9514 LU-10513 Development End date Fri, 29 Apr 2016 11:03:53 +0000 Rank 1|hzxu5r: Rank (Obsolete) 9223372036854775807 Start date Tue, 24 Nov 2015 11:03:53 +0000