<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:15:43 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-8225] router node: Failed to create FMR pool: -38</title>
                <link>https://jira.whamcloud.com/browse/LU-8225</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;On a router node with both omnipath and mellanox interfaces, I see the following in the output of journalctl -xe:&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;-- Unit lnet.service has begun starting up.
kernel: LNet: Added LNI 192.168.128.187@o2ib18 [128/8192/0/180]
kernel: fmr_pool: Device mlx5_0 does not support FMRs
kernel: LNetError: 7963:0:(o2iblnd.c:1459:kiblnd_create_fmr_pool()) Failed to create FMR pool: -38
kernel: LNetError: 7963:0:(o2iblnd.c:2096:kiblnd_net_init_pools()) Can&apos;t initialize FMR pool for CPT 0: -38
kernel: LNetError: 7963:0:(o2iblnd.c:2895:kiblnd_startup()) Failed to initialize NI pools: -38
kernel: LNetError: 105-4: Error -100 starting up LNI o2ib
kernel: LNetError: 801:0:(o2iblnd_cb.c:2297:kiblnd_passive_connect()) Can&apos;t accept conn from 192.168.128.37@o2ibkernel: LNetError: 801:0:(o2iblnd_cb.c:2297:kiblnd_passive_connect()) Skipped 20 previous similar messages
kernel: LNet: Removed LNI 192.168.128.187@o2ib18
lnet[7960]: LNET configure error 100: Network is down
systemd[1]: lnet.service: control process exited, code=exited status=1
systemd[1]: Failed to start SYSV: Part of the lustre file system..
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I do not encounter this on the compute nodes, which have only omnipath, nor on the lustre servers, which have only mellanox.&lt;/p&gt;

&lt;p&gt;Lustre 2.8 ships with /etc/modprobe.d/ko2iblnd.conf, which contains:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;alias ko2iblnd-opa ko2iblnd
options ko2iblnd-opa peer_credits=128 peer_credits_hiw=64 credits=1024 concurrent_sends=256 ntx=2048 map_on_demand=32 fmr_pool_size=2048 fmr_flush_trigger=512 fmr_cache=1
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment>RHEL7.2 derivative:  3.10.0-327.13.1.3chaos.ch6.x86_64 #1 SMP Wed May 11 18:38:20 PDT 2016 x86_64 x86_64 x86_64 GNU/Linux&lt;br/&gt;
lustre-2.8.0_0.0.llnlpreview.13-1.ch6.x86_64&lt;br/&gt;
router has two interfaces, omnipath on compute side:&lt;br/&gt;
05:00.0 Infiniband controller: Mellanox Technologies MT27700 Family [ConnectX-4]&lt;br/&gt;
81:00.0 Fabric controller: Intel Corporation Omni-Path HFI Silicon 100 Series [discrete] (rev 10)</environment>
        <key id="37298">LU-8225</key>
            <summary>router node: Failed to create FMR pool: -38</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.whamcloud.com/images/icons/priorities/major.svg">Major</priority>
                        <status id="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="3">Duplicate</resolution>
                                        <assignee username="dmiter">Dmitry Eremin</assignee>
                                    <reporter username="ofaaland">Olaf Faaland</reporter>
                        <labels>
                            <label>llnl</label>
                    </labels>
                <created>Wed, 1 Jun 2016 01:25:50 +0000</created>
                <updated>Wed, 1 Jun 2016 15:59:07 +0000</updated>
                            <resolved>Wed, 1 Jun 2016 15:59:07 +0000</resolved>
                                    <version>Lustre 2.8.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="154190" author="ofaaland" created="Wed, 1 Jun 2016 01:26:57 +0000"  >&lt;p&gt;This did not come up with lustre 2.5; it&apos;s new with lustre 2.8.&lt;/p&gt;</comment>
                            <comment id="154191" author="ofaaland" created="Wed, 1 Jun 2016 01:27:46 +0000"  >&lt;p&gt;Note this occurs when attempt to start lnet.  Lnet fails to start as a result.&lt;/p&gt;</comment>
                            <comment id="154195" author="ofaaland" created="Wed, 1 Jun 2016 01:44:44 +0000"  >&lt;p&gt;Removing /etc/modprobe.d/ko2iblnd.conf allows lnet to start successfully.  lctl pings from client-&amp;gt;server and server-&amp;gt;client (through the router) then work as expected.&lt;/p&gt;</comment>
                            <comment id="154223" author="pjones" created="Wed, 1 Jun 2016 11:45:21 +0000"  >&lt;p&gt;Olaf&lt;/p&gt;

&lt;p&gt;It seems that this is a duplicate of &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5783&quot; title=&quot;o2iblnd: investigate new memory registration mechanisms&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5783&quot;&gt;&lt;del&gt;LU-5783&lt;/del&gt;&lt;/a&gt; which is queued up for inclusion in the 2.8.1 FE release - &lt;a href=&quot;http://review.whamcloud.com/#/c/19024/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/19024/&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Dmitry &lt;/p&gt;

&lt;p&gt;Please can you provide any further advise LLNL need on this topic&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="154256" author="ofaaland" created="Wed, 1 Jun 2016 15:36:00 +0000"  >&lt;p&gt;Peter,&lt;br/&gt;
I agree this is a duplicate.  Thanks for finding the original.  If Dmitry has no other comments feel free to close this ticket.&lt;br/&gt;
thanks,&lt;br/&gt;
Olaf&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzydav:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>