<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:33:59 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-3446] changelog index reset on MDT restart</title>
                <link>https://jira.whamcloud.com/browse/LU-3446</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;After a maintenance downtime in which we updated our vesta Lustre servers from 2.4.0-RC1_3chaos to 2.4.0-RC2_2chaos, the changelog current index reverted to zero.  The registered user cl1 retained its highest index value:&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;# vesta-mds1 /root &amp;gt; lctl get_param mdd.fsv MDT0000.changelog_users                                                                     
mdd.fsv-MDT0000.changelog_users=
current index: 9158128
ID    index
cl1   445461827
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Here is a debug log entry from when the MDS started:&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;00000004:00000080:1.0:1370534969.929148:0:17901:0:(mdd_device.c:308:mdd_changelog_llog_init()) changelog starting index=0
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;LLNL-bug-id: TOSS-2103&lt;/p&gt;</description>
                <environment>mds: lustre-2.4.0-RC2_2chaos_2.6.32_358.6.1.3chaos.ch5.1.ch5.1.x86_64</environment>
        <key id="19324">LU-3446</key>
            <summary>changelog index reset on MDT restart</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="2" iconUrl="https://jira.whamcloud.com/images/icons/priorities/critical.svg">Critical</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="1">Fixed</resolution>
                                        <assignee username="bobijam">Zhenyu Xu</assignee>
                                    <reporter username="nedbass">Ned Bass</reporter>
                        <labels>
                            <label>HB</label>
                            <label>changelog</label>
                    </labels>
                <created>Fri, 7 Jun 2013 23:52:51 +0000</created>
                <updated>Tue, 20 Aug 2013 20:24:23 +0000</updated>
                            <resolved>Tue, 20 Aug 2013 20:24:22 +0000</resolved>
                                    <version>Lustre 2.4.0</version>
                                    <fixVersion>Lustre 2.4.1</fixVersion>
                    <fixVersion>Lustre 2.5.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>8</watches>
                                                                            <comments>
                            <comment id="60215" author="pjones" created="Sat, 8 Jun 2013 14:18:55 +0000"  >&lt;p&gt;Bobijam&lt;/p&gt;

&lt;p&gt;Could you please help with this one?&lt;/p&gt;

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

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="60221" author="bobijam" created="Sun, 9 Jun 2013 01:32:47 +0000"  >&lt;p&gt;the mdd_device.c:308 is from mdd initialize LLOG_CHANGELOG_ORIG_CTXT, after that, we come to LLOG_CHANGELOG_USER_ORIG_CTXT initialization, where in changelog_user_init_cb(), it sets mdd-&amp;gt;mdd_cl.mc_lastuser, then we go back to mdd_change_llog_init()&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;        &lt;span class=&quot;code-comment&quot;&gt;/* If we have registered users, assume we want changelogs on */&lt;/span&gt;
        &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; (mdd-&amp;gt;mdd_cl.mc_lastuser &amp;gt; 0) {
                rc = mdd_changelog_on(env, mdd, 1);
                &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; (rc &amp;lt; 0)
                        GOTO(out_uclose, rc);
        }
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;And mdd_changelog_on() &lt;del&gt;&amp;gt; mdd_changelog_write_head(), it adds back mdd&lt;/del&gt;&amp;gt;mdd_cl.mc_index.&lt;/p&gt;</comment>
                            <comment id="60252" author="adilger" created="Mon, 10 Jun 2013 15:28:07 +0000"  >&lt;p&gt;Bobijam, does your comment indicate that this should not be an actual problem?  Do we have a ChangeLog test that verifies the ChangeLog index after a restart?&lt;/p&gt;</comment>
                            <comment id="60512" author="bobijam" created="Thu, 13 Jun 2013 02:45:09 +0000"  >&lt;p&gt;Ned,&lt;/p&gt;

&lt;p&gt;When did the cl1 changelog_users read happen, after the MDT restart?&lt;/p&gt;

&lt;p&gt;Here&apos;s my local VM situation.&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;[10:38 AM]root@test1:~/work/lustre/lustre/tests/
# lctl get_param mdd.lustre-MDT0000.changelog_users
mdd.lustre-MDT0000.changelog_users=current index: 58
ID    index
cl1   0
cl2   37

[10:42 AM]root@test1:~/work/lustre/lustre/tests/
# umount /mnt/mds1

[10:43 AM]root@test1:~/work/lustre/lustre/tests/
# mount -t lustre /dev/sdb /mnt/mds1

[10:43 AM]root@test1:~/work/lustre/lustre/tests/
# lctl get_param mdd.lustre-MDT0000.changelog_users
mdd.lustre-MDT0000.changelog_users=current index: 58
ID    index
cl1   0
cl2   37
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                            <comment id="60571" author="nedbass" created="Thu, 13 Jun 2013 17:00:35 +0000"  >&lt;p&gt;Bobijam, yes, the cl1 changelog_users users in the description happened after the MDT restart.&lt;/p&gt;

&lt;p&gt;Before this update, the current index was preserved between MDT restarts (as far as I know).&lt;/p&gt;

&lt;p&gt;We had a reboot yesterday, and, now that I check, it appears that the index was again reset:&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;# vesta-mds1 /root &amp;gt; lctl get_param mdd.fsv-MDT0000.changelog_users
mdd.fsv-MDT0000.changelog_users=
current index: 444830
ID    index
cl1   445461827
cl2   18248038
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                            <comment id="60586" author="nedbass" created="Thu, 13 Jun 2013 19:50:19 +0000"  >&lt;p&gt;It seems that if the registered changelog user has cleared all changelog records when the MDT is stopped, then when the MDT restarts &lt;tt&gt;changelog_init_cb()&lt;/tt&gt; is never called from &lt;tt&gt;llog_reverse_process()&lt;/tt&gt;, so &lt;tt&gt;mdd-&amp;gt;mdd_cl.mc_index&lt;/tt&gt; is left with 0.&lt;/p&gt;

&lt;p&gt;This reproduces the problem in a VM for me:&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;FSTYPE=zfs llmount.sh
lctl --device lustre-MDT0000 changelog_register
touch /mnt/lustre/{1,2,3,4}
lfs changelog_clear lustre-MDT0000 cl1 4
umount /mnt/mds1
mount.lustre lustre-mdt1/mdt1  /mnt/mds1
lctl get_param mdd.lustre-MDT0000.changelog_users
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
</comment>
                            <comment id="60603" author="nedbass" created="Thu, 13 Jun 2013 22:51:57 +0000"  >&lt;p&gt;Path for master:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/#change,6642&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#change,6642&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="60776" author="morrone" created="Mon, 17 Jun 2013 17:57:10 +0000"  >&lt;p&gt;This needs to be fixed for 2.4.1 as well, so you should really added that Fix Version as well.&lt;/p&gt;</comment>
                            <comment id="62425" author="jlevi" created="Tue, 16 Jul 2013 20:51:25 +0000"  >&lt;p&gt;When should we expect to see the patch for 2.4.1?&lt;/p&gt;</comment>
                            <comment id="62430" author="nedbass" created="Tue, 16 Jul 2013 21:52:52 +0000"  >&lt;p&gt;Patch for b2_4:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/#/c/7012/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/7012/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="64668" author="pjones" created="Tue, 20 Aug 2013 20:24:23 +0000"  >&lt;p&gt;Landed for 2.4.1 and 2.5&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|hzvsxr:</customfieldvalue>

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