<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:14:50 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-1238] record_lcfg() failed with ENOSPC</title>
                <link>https://jira.whamcloud.com/browse/LU-1238</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;While running ost-pools test 5 with 2000 OSTs, after adding 2000 OSTs to one OST pool and then removing the OSTs from the pool, the test failed as follows:&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;~snip~&amp;gt;
client-19-ib: Warning, OST lustre-OST041f_UUID still found in pool lustre.testpool
client-19-ib: Warning, OST lustre-OST0420_UUID still found in pool lustre.testpool
&amp;lt;~snip~&amp;gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Console log on the combined MGS/MDS showed that:&lt;/p&gt;
&lt;div class=&quot;panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;panelContent&quot;&gt;
&lt;p&gt;&lt;font color=&quot;red&quot;&gt;LustreError: 16312:0:(mgs_llog.c:752:record_lcfg()) failed -28&lt;/font&gt;&lt;br/&gt;
LustreError: 16340:0:(mgs_llog.c:752:record_lcfg()) failed -28&lt;br/&gt;
LustreError: 16340:0:(mgs_llog.c:788:record_base()) error -28: lcfg lustre-MDT0000-mdtlov 0xce022 lustre testpool lustre-OST041f_UUID (null)&lt;br/&gt;
LustreError: 16340:0:(mgs_llog.c:788:record_base()) error -28: lcfg lustre-clilov 0xce022 lustre testpool lustre-OST041f_UUID (null)&lt;br/&gt;
LustreError: 16369:0:(mgs_llog.c:752:record_lcfg()) failed -28&lt;br/&gt;
LustreError: 16369:0:(mgs_llog.c:752:record_lcfg()) Skipped 5 previous similar messages&lt;br/&gt;
LustreError: 16369:0:(mgs_llog.c:788:record_base()) error -28: lcfg lustre-MDT0000-mdtlov 0xce022 lustre testpool lustre-OST0420_UUID (null)&lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Maloo report: &lt;a href=&quot;https://maloo.whamcloud.com/test_sets/a610c4b2-71cd-11e1-9716-5254004bbbd3&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://maloo.whamcloud.com/test_sets/a610c4b2-71cd-11e1-9716-5254004bbbd3&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;By running llog_reader on CONFIGS/lustre-MDT0000 file on the MGS/MDS node, I found there were 63293 records in that file and 1474 bits were not set. The last several records are:&lt;/p&gt;
&lt;div class=&quot;panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;panelContent&quot;&gt;
&lt;p&gt;#64763 (224)marker 2043193 (flags=0x01, v2.2.0.0) lustre-MDT0000-mdtlov &apos;rem lustre.testpool.lustre-OST041d_UUID&apos; Mon Mar 19 03:01:52 2012-&lt;br/&gt;
#64764 (144)pool remove 0:lustre-MDT0000-mdtlov  1:lustre  2:testpool  3:lustre-OST041d_UUID&lt;br/&gt;
#64765 (224)marker 2043193 (flags=0x02, v2.2.0.0) lustre-MDT0000-mdtlov &apos;rem lustre.testpool.lustre-OST041d_UUID&apos; Mon Mar 19 03:01:52 2012-&lt;br/&gt;
#64766 (224)marker 2043195 (flags=0x01, v2.2.0.0) lustre-MDT0000-mdtlov &apos;rem lustre.testpool.lustre-OST041e_UUID&apos; Mon Mar 19 03:02:02 2012-&lt;br/&gt;
&lt;font color=&quot;red&quot;&gt;#64767&lt;/font&gt; (144)pool remove 0:lustre-MDT0000-mdtlov  1:lustre  2:testpool  3:lustre-OST041e_UUID&lt;/p&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The OST pool operations consumed most of the records and caused the record count reach to the following limitation:&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;         /* if it&apos;s the last idx in log file, then return -ENOSPC */
         if (loghandle-&amp;gt;lgh_last_idx &amp;gt;= LLOG_BITMAP_SIZE(llh) - 1)
                 RETURN(-ENOSPC);
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&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;/* (8192 - 88 - 8) * 8 = 64768 */
#define LLOG_BITMAP_SIZE(llh)  ((llh-&amp;gt;llh_hdr.lrh_len -         \
                                 llh-&amp;gt;llh_bitmap_offset -       \
                                 sizeof(llh-&amp;gt;llh_tail)) * 8)
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Please find the attached lustre-MDT0000.log for the output of &quot;llog_reader lustre-MDT0000&quot; and see how to resolve this issue.&lt;/p&gt;</description>
                <environment>&lt;br/&gt;
Lustre Tag: v2_2_0_0_RC1&lt;br/&gt;
Lustre Build: &lt;a href=&quot;https://build.whamcloud.com/job/lustre-b2_2/11&quot;&gt;https://build.whamcloud.com/job/lustre-b2_2/11&lt;/a&gt;&lt;br/&gt;
Distro/Arch: RHEL6.2/x86_64 (kernel version: 2.6.32-220.4.2.el6)&lt;br/&gt;
&lt;br/&gt;
OSSCOUNT=2&lt;br/&gt;
OSTCOUNT=2000 (with 1000 OSTs per OSS)&lt;br/&gt;
NETTYPE=o2ib&lt;br/&gt;
ENABLE_QUOTA=yes&lt;br/&gt;
</environment>
        <key id="13625">LU-1238</key>
            <summary>record_lcfg() failed with ENOSPC</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="5">Cannot Reproduce</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="yujian">Jian Yu</reporter>
                        <labels>
                    </labels>
                <created>Tue, 20 Mar 2012 06:01:19 +0000</created>
                <updated>Mon, 29 May 2017 03:36:00 +0000</updated>
                            <resolved>Mon, 29 May 2017 03:36:00 +0000</resolved>
                                    <version>Lustre 2.2.0</version>
                    <version>Lustre 2.3.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="44473" author="adilger" created="Mon, 10 Sep 2012 02:02:33 +0000"  >&lt;p&gt;Two problems are visible in this config log:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;there appear to be thousands of &quot;set_timeout=20&quot; lines that are added, possibly by test-framework.sh?  That definitely doesn&apos;t help matters&lt;/li&gt;
	&lt;li&gt;I&apos;m not sure anymore why we have the &lt;tt&gt;marker&lt;/tt&gt; lines in the config logs.  I think these are only comments, but they aren&apos;t very useful in the case of single-line records, especially when there are two &lt;tt&gt;marker&lt;/tt&gt; lines for every single record added.  While this won&apos;t solve the problem being seen here, it will push it 3x further away.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Alex has recently been reworking how config llogs are processed by the servers, and I wonder if we could simplify this for newer clients as well?  Maybe we don&apos;t even need &lt;tt&gt;marker&lt;/tt&gt; lines anymore, or we can figure a way not to need them.  Similarly, newer servers do not need so many lines to configure their device stack, maybe clients could become more intelligent as well (i.e. given a record with OST+NIDs they can figure everything else out)?&lt;/p&gt;</comment>
                            <comment id="197368" author="adilger" created="Mon, 29 May 2017 03:36:00 +0000"  >&lt;p&gt;Close old ticket.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="10977" name="lustre-MDT0000.log" size="8001426" author="yujian" created="Tue, 20 Mar 2012 06:01:19 +0000"/>
                    </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|hzw4rr:</customfieldvalue>

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