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-8912 Lustre <p>Hi, we noticed the following minor issue when trying to add our IB network 10.210.32.0/20 to nodemap:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">$ lctl nodemap_add_range --name sherlock --range 10.210.[32-47].[0-255]@o2ib3 error: nodemap_add_range: nodemap ranges must be contiguous $ cat /proc/fs/lustre/nodemap/sherlock/ranges [ ] </pre> </div></div> <p>The workaround is either to add 16 separate entries (10.210.32.<span class="error">&#91;0-255&#93;</span>, 10.210.33.<span class="error">&#91;0-255&#93;</span> etc.), or a single larger range (whenever possible).</p> <p>Thanks,<br/> Stephan</p> CentOS 7.2, Lustre-2.8.60 LU-8912

nodemap: error: nodemap_add_range: nodemap ranges must be contiguous

Bug Minor Resolved Fixed Kit Westneat Stephane Thiell Tue, 6 Dec 2016 19:52:17 +0000 Mon, 9 Apr 2018 22:22:50 +0000 Sat, 3 Mar 2018 14:02:13 +0000 Lustre 2.9.0 Lustre 2.11.0 Lustre 2.10.4 0 5 <p>Kit</p> <p>Could you please advise on this issue?</p> <p>Thanks</p> <p>Peter</p> <p>I'm not sure how the contiguous ranges is figured out, I'll try to see how hard it would be to get this to work. </p> <p>It looks like the LNET range parsing is currently not complete, and broken in parts. It would be much easier to use a subset of the range. The full LNET range syntax supports multiple NID expressions and multiple range expressions within the NID expressions. For example, these are both valid:<br/> lctl nodemap_add_range --name c0 --range "10.210.1.<span class="error">&#91;0-255&#93;</span>@tcp 10.210.2.0@tcp"<br/> lctl nodemap_add_range --name c0 --range "10.210.1.<span class="error">&#91;33,31,32&#93;</span>@tcp"</p> <p>It would be significantly easier to parse if we only allow a single NID expression per range, and a single range expression per IP expression list.</p> <p>Alternatively, lctl actually just converts the range syntax into a simpler one read by the MGS, which is just &lt;first nid&gt;:&lt;last nid&gt;. Would it be too confusing to have sysadmins use that directly?</p> <p>Hi Kit,</p> <p>Thanks for looking at this! It would be better if the sysadmin can just add &lt;first nid&gt;:&lt;last nid&gt;, as it is already the format used internally by the MGS and also used when accessing the nodemap range config (using /proc/fs/lustre/nodemap/sherlock/ranges for example). I am sure it would be less confusing after all, along with the restrictions of range syntax that you propose to avoid any mistakes.</p> <p>I tend to agree with you, but on our nodemap call, Intel voiced a strong preference for supporting the full LNET range expression support. I've prepared a bug fix patch to address your immediate issue. </p> <p>The idea behind the full LNET range support is that instead of requiring non-contiguous ranges, if a non-contiguous range is given to lctl, multiple contiguous ranges will be created in the backend. I'll create an improvement ticket to track the work on that.</p> <p>Kit Westneat (kit.westneat@gmail.com) uploaded a new patch: <a href="https://review.whamcloud.com/24397" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/24397</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-8912" title="nodemap: error: nodemap_add_range: nodemap ranges must be contiguous" class="issue-link" data-issue-key="LU-8912"><del>LU-8912</del></a> nodemap: fix contiguous range support<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: f9bf47f8590cdd77a7b896eea7e83e91782f04bd</p> <p><a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=kit.westneat" class="user-hover" rel="kit.westneat">kit.westneat</a>, please rebase the patch manually. thanks</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="https://review.whamcloud.com/24397/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/24397/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-8912" title="nodemap: error: nodemap_add_range: nodemap ranges must be contiguous" class="issue-link" data-issue-key="LU-8912"><del>LU-8912</del></a> nodemap: fix contiguous range support<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: eac95a6587af4061b36b35051e191ca27bc6b1a3</p> <p>Landed for 2.11</p> <p>Minh Diep (minh.diep@intel.com) uploaded a new patch: <a href="https://review.whamcloud.com/31521" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/31521</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-8912" title="nodemap: error: nodemap_add_range: nodemap ranges must be contiguous" class="issue-link" data-issue-key="LU-8912"><del>LU-8912</del></a> nodemap: fix contiguous range support<br/> Project: fs/lustre-release<br/> Branch: b2_10<br/> Current Patch Set: 1<br/> Commit: 1f9c0431a29e2f0a8cac90eef9ae0dfa18b02cae</p> <p>John L. Hammond (john.hammond@intel.com) merged in patch <a href="https://review.whamcloud.com/31521/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/31521/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-8912" title="nodemap: error: nodemap_add_range: nodemap ranges must be contiguous" class="issue-link" data-issue-key="LU-8912"><del>LU-8912</del></a> nodemap: fix contiguous range support<br/> Project: fs/lustre-release<br/> Branch: b2_10<br/> Current Patch Set: <br/> Commit: 92d562457b947f02891e7c76b265bde4f9ed23c2</p> Related Development Rank 1|hzyxmv: Rank (Obsolete) 9223372036854775807 Severity