<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:45:10 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-4709] Can&apos;t allocate super-sequence, rc -115</title>
                <link>https://jira.whamcloud.com/browse/LU-4709</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;In setting up a Lustre 2.5.0 environment I am encountering an error.&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;&amp;lt;normal lustre mount messages&amp;gt;
 23:35:56 lotus-24 kernel: LDISKFS-fs (sdk8): mounted filesystem with ordered data mode. quota=on. Opts:
Mar  3 23:35:56 lotus-24 kernel: LDISKFS-fs (sdk8): mounted filesystem with ordered data mode. quota=on. Opts:
Mar  3 23:35:57 lotus-24 kernel: LDISKFS-fs (sdk8): mounted filesystem with ordered data mode. quota=on. Opts:
Mar  3 23:42:18 lotus-24 kernel: LustreError: 17341:0:(fid_handler.c:286:__seq_server_alloc_meta()) srv-testfs-OST000f: Can&apos;t allocate super-sequence, rc -115
Mar  3 23:42:18 lotus-24 kernel: LustreError: 17341:0:(fid_handler.c:286:__seq_server_alloc_meta()) Skipped 1392 previous similar messages
Mar  3 23:52:18 lotus-24 kernel: LustreError: 15693:0:(fid_handler.c:286:__seq_server_alloc_meta()) srv-testfs-OST0002: Can&apos;t allocate super-sequence, rc -115
Mar  3 23:52:18 lotus-24 kernel: LustreError: 15693:0:(fid_handler.c:286:__seq_server_alloc_meta()) Skipped 1477 previous similar messages
Mar  4 00:02:18 lotus-24 kernel: LustreError: 17341:0:(fid_handler.c:286:__seq_server_alloc_meta()) srv-testfs-OST001b: Can&apos;t allocate super-sequence, rc -115
Mar  4 00:02:18 lotus-24 kernel: LustreError: 17341:0:(fid_handler.c:286:__seq_server_alloc_meta()) Skipped 1466 previous similar messages
Mar  4 00:12:19 lotus-24 kernel: LustreError: 15693:0:(fid_handler.c:286:__seq_server_alloc_meta()) srv-testfs-OST0009: Can&apos;t allocate super-sequence, rc -115
Mar  4 00:12:19 lotus-24 kernel: LustreError: 15693:0:(fid_handler.c:286:__seq_server_alloc_meta()) Skipped 1477 previous similar messages
Mar  4 00:22:20 lotus-24 kernel: LustreError: 17341:0:(fid_handler.c:286:__seq_server_alloc_meta()) srv-testfs-OST0018: Can&apos;t allocate super-sequence, rc -115


.....
08:52:34 lotus-24 kernel: LustreError: 17341:0:(fid_handler.c:286:__seq_server_alloc_meta()) srv-testfs-OST0004: Can&apos;t allocate super-sequence, rc -115
Mar  4 08:52:34 lotus-24 kernel: LustreError: 17341:0:(fid_handler.c:286:__seq_server_alloc_meta()) Skipped 1474 previous similar messages
Mar  4 09:02:34 lotus-24 kernel: LustreError: 22775:0:(fid_handler.c:286:__seq_server_alloc_meta()) srv-testfs-OST000f: Can&apos;t allocate super-sequence, rc -115
Mar  4 09:02:34 lotus-24 kernel: LustreError: 22775:0:(fid_handler.c:286:__seq_server_alloc_meta()) Skipped 1470 previous similar messages
Mar  4 09:12:34 lotus-24 kernel: LustreError: 17341:0:(fid_handler.c:286:__seq_server_alloc_meta()) srv-testfs-OST0002: Can&apos;t allocate super-sequence, rc -115
Mar  4 09:12:34 lotus-24 kernel: LustreError: 17341:0:(fid_handler.c:286:__seq_server_alloc_meta()) Skipped 1477 previous similar messages
Mar  4 09:22:34 lotus-24 kernel: LustreError: 15693:0:(fid_handler.c:286:__seq_server_alloc_meta()) srv-testfs-OST001b: Can&apos;t allocate super-sequence, rc -115
Mar  4 09:22:34 lotus-24 kernel: LustreError: 15693:0:(fid_handler.c:286:__seq_server_alloc_meta()) Skipped 1466 previous similar messages
Mar  4 09:32:35 lotus-24 kernel: LustreError: 20339:0:(fid_handler.c:286:__seq_server_alloc_meta()) srv-testfs-OST0009: Can&apos;t allocate super-sequence, rc -115
Mar  4 09:32:35 lotus-24 kernel: LustreError: 20339:0:(fid_handler.c:286:__seq_server_alloc_meta()) Skipped 1477 previous similar messages
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;


&lt;p&gt;df shows all the OSTs mounted and present but trying to mount the namespace on a Client seems to reboot the systems. &lt;/p&gt;

&lt;p&gt;As present there are 27 or so OSTs and a MDT on this server, this same behavior is seen on pure OSSs.  The Lustre targets are physically slow. &lt;/p&gt;


</description>
                <environment>Lustre 2.5.0 Development environment, system is fresh and /scratch  </environment>
        <key id="23457">LU-4709</key>
            <summary>Can&apos;t allocate super-sequence, rc -115</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</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="6">Not a Bug</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="keith">Keith Mannthey</reporter>
                        <labels>
                    </labels>
                <created>Tue, 4 Mar 2014 17:58:16 +0000</created>
                <updated>Wed, 5 Mar 2014 01:34:47 +0000</updated>
                            <resolved>Wed, 5 Mar 2014 01:34:47 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                            <comments>
                            <comment id="78380" author="keith" created="Tue, 4 Mar 2014 19:36:54 +0000"  >&lt;p&gt;It can also been seen in mount blocks like:&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;LDISKFS-fs (sdk3): mounted filesystem with ordered data mode. quota=on. Opts: 
LDISKFS-fs (sdk3): mounted filesystem with ordered data mode. quota=on. Opts: 
LDISKFS-fs (sdk3): mounted filesystem with ordered data mode. quota=on. Opts: 
Lustre: testfs-OST0011: new disk, initializing
Lustre: Skipped 8 previous similar messages
LustreError: 13a-8: Failed to get MGS log params and no local copy.
LustreError: Skipped 17 previous similar messages
LustreError: 44563:0:(fid_handler.c:286:__seq_server_alloc_meta()) srv-testfs-OST0001: Can&apos;t allocate super-sequence, rc -115
LustreError: 44563:0:(fid_handler.c:286:__seq_server_alloc_meta()) Skipped 340 previous similar messages
LDISKFS-fs (sdk5): mounted
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                            <comment id="78428" author="keith" created="Wed, 5 Mar 2014 01:33:45 +0000"  >&lt;p&gt;Well it seems this is what happens when you create a -mdt -mgt with index=1 instead of index=0 (when you only have a single MDT).  User error off-by-one. &lt;/p&gt;</comment>
                            <comment id="78429" author="keith" created="Wed, 5 Mar 2014 01:34:47 +0000"  >&lt;p&gt;Something less then a client crash would be nice but it was user error. &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|hzwgq7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>12946</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>