<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:17:41 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-1556] MDS does not register changelog readers</title>
                <link>https://jira.whamcloud.com/browse/LU-1556</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Customer uses changelog to watch the filesystem. For some weeks it&apos;s been properly working but now we observe several problems on the changelog functionality. These problems do not allow us to properly use changelog:&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@xxx14 ~&amp;#93;&lt;/span&gt;# lctl --device project-MDT0000 changelog_register&lt;br/&gt;
project-MDT0000: Registered changelog userid &apos;cl6&apos;&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;root@xxx14 ~&amp;#93;&lt;/span&gt;# cat /proc/fs/lustre/mdd/project-MDT0000/changelog_users&lt;br/&gt;
current index: 5077892&lt;br/&gt;
ID    index&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;root@helios14 ~&amp;#93;&lt;/span&gt;# lctl --device project-MDT0000 changelog_deregister cl6&lt;br/&gt;
error: changelog_deregister: Invalid argument&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;root@helios14 ~&amp;#93;&lt;/span&gt;# cat /proc/fs/lustre/mdd/project-MDT0000/changelog_mask &lt;br/&gt;
MARK CREAT MKDIR HLINK SLINK MKNOD UNLNK RMDIR RNMFM RNMTO OPEN CLOSE IOCTL TRUNC SATTR XATTR HSM MTIME CTIME &lt;/p&gt;


&lt;p&gt;Trying to read changelog sequence starts at 3200000, so it&apos;s like if there was still one client reader not having cleared further entries. &lt;/p&gt;

&lt;p&gt;Tryning to clear every client reader does not change anything:&lt;br/&gt;
for i in 1 2 3 4 5 6 ; do lfs changelog_clear project-MDT0000 cl$i 5000000 ; done&lt;/p&gt;

&lt;p&gt;And in MDS&apos; syslog:&lt;br/&gt;
1340367641 2012 Jun 22 21:20:41 helios14 kern warning kernel Lustre: 9270:0:(mdd_device.c:1478:mdd_changelog_user_purge()) Could not determine changelog records to purge; rc=-22&lt;br/&gt;
1340367641 2012 Jun 22 21:20:41 helios14 kern warning kernel Lustre: 9270:0:(mdd_device.c:1478:mdd_changelog_user_purge()) Skipped 3 previous similar messages&lt;/p&gt;

&lt;p&gt;Changelogs can be read but not cleared, thus affecting the tool reading changelogs.&lt;/p&gt;

&lt;p&gt;This issue arises with lustre-2.1.1.&lt;/p&gt;

&lt;p&gt;Does this sound as a known problem for you? How could we have more debugging information while system is in production?&lt;/p&gt;</description>
                <environment></environment>
        <key id="15006">LU-1556</key>
            <summary>MDS does not register changelog readers</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="6" iconUrl="https://jira.whamcloud.com/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="5">Cannot Reproduce</resolution>
                                        <assignee username="ys">Yang Sheng</assignee>
                                    <reporter username="dmoreno">Diego Moreno</reporter>
                        <labels>
                    </labels>
                <created>Fri, 22 Jun 2012 08:41:37 +0000</created>
                <updated>Mon, 16 Mar 2015 07:39:49 +0000</updated>
                            <resolved>Tue, 6 Jan 2015 14:43:48 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>8</watches>
                                                                            <comments>
                            <comment id="41030" author="pjones" created="Fri, 22 Jun 2012 09:25:36 +0000"  >&lt;p&gt;Yangsheng&lt;/p&gt;

&lt;p&gt;Could you please look into this one?&lt;/p&gt;

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

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="41060" author="ys" created="Sun, 24 Jun 2012 11:32:10 +0000"  >&lt;p&gt;Hi, Diego, Could you upload more logs in there? Especially the context of &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;1340367641 2012 Jun 22 21:20:41 helios14 kern warning kernel Lustre: 9270:0:(mdd_device.c:1478:mdd_changelog_user_purge()) Could not determine changelog records to purge; rc=-22
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                            <comment id="41092" author="dmoreno" created="Mon, 25 Jun 2012 10:38:35 +0000"  >&lt;p&gt;As I couldn&apos;t upload the dmesg file via jira I uploaded it in whamcloud&apos;s ftp. Please, find there the dmesg file with some llog errors I couldn&apos;t understand.&lt;/p&gt;

&lt;p&gt;We often see this message:&lt;br/&gt;
LustreError: 9178:0:(llog_lvfs.c:473:llog_lvfs_next_block()) Invalid llog tail at log id 670040609/1607149776 offset 16384&lt;/p&gt;</comment>
                            <comment id="41236" author="ys" created="Thu, 28 Jun 2012 00:40:27 +0000"  >&lt;p&gt;Thanks, Diego, This is very useful.&lt;/p&gt;</comment>
                            <comment id="41365" author="dmoreno" created="Mon, 2 Jul 2012 08:53:05 +0000"  >&lt;p&gt;Some more logs (lustre debug file). Log has been enabled just before running &quot;lctl --device MDT0000 changelog_register&quot;.&lt;/p&gt;

&lt;p&gt;It seems there&apos;s an invalid entry on changelog but how could this entry be there?? and how can we remove this bad entry??&lt;/p&gt;

&lt;p&gt;If you need the entire file, please ask.&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; 
00000040:00020000:1.0:1340966614.416509:0:24262:0:(llog_lvfs.c:473:llog_lvfs_next_block()) Invalid llog tail at log id 670040609/1607149776 offset 16384
00000040:00020000:8.0:1340966614.427773:0:24264:0:(llog_lvfs.c:473:llog_lvfs_next_block()) Invalid llog tail at log id 670040609/1607149776 offset 16384
00000004:02000000:1.0:1340966671.265493:0:24267:0:(mdd_device.c:270:mdd_changelog_on()) mdd_obd-project-MDT0000: changelog on
00000004:00020000:1.0:1340966671.269665:0:24267:0:(mdd_device.c:274:mdd_changelog_on()) Changelogs cannot be enabled due to error condition (see mdd_obd-project-MDT0000 log).
00000040:00020000:1.0:1340966683.106474:0:24270:0:(llog_lvfs.c:473:llog_lvfs_next_block()) Invalid llog tail at log id 670040609/1607149776 offset 16384
00000040:00020000:1.0:1340966683.126397:0:24272:0:(llog_lvfs.c:473:llog_lvfs_next_block()) Invalid llog tail at log id 670040609/1607149776 offset 16384
00000004:02000000:1.0:1340966711.276400:0:24275:0:(mdd_device.c:270:mdd_changelog_on()) mdd_obd-project-MDT0000: changelog on
00000004:00020000:1.0:1340966711.280559:0:24275:0:(mdd_device.c:274:mdd_changelog_on()) Changelogs cannot be enabled due to error condition (see mdd_obd-project-MDT0000 log).
00000040:00020000:1.0:1340966721.286568:0:24279:0:(llog_lvfs.c:473:llog_lvfs_next_block()) Invalid llog tail at log id 670040609/1607149776 offset 16384
00000004:00000400:6.0:1340966721.306381:0:24277:0:(mdd_device.c:1478:mdd_changelog_user_purge()) Could not determine changelog records to purge; rc=-22
00000004:02000000:7.0:1340966758.786405:0:24281:0:(mdd_device.c:270:mdd_changelog_on()) mdd_obd-project-MDT0000: changelog on
00000004:00020000:7.0:1340966758.790585:0:24281:0:(mdd_device.c:274:mdd_changelog_on()) Changelogs cannot be enabled due to error condition (see mdd_obd-project-MDT0000 log).
00000040:00020000:1.0:1340967087.617075:0:24326:0:(llog_lvfs.c:473:llog_lvfs_next_block()) Invalid llog tail at log id 670040609/1607149776 offset 16384
00000040:00020000:8.0:1340967087.628338:0:24328:0:(llog_lvfs.c:473:llog_lvfs_next_block()) Invalid llog tail at log id 670040609/1607149776 offset 16384
00000004:02000000:1.0:1340967087.629959:0:24329:0:(mdd_device.c:270:mdd_changelog_on()) mdd_obd-project-MDT0000: changelog on
00000004:00020000:1.0:1340967087.635292:0:24329:0:(mdd_device.c:274:mdd_changelog_on()) Changelogs cannot be enabled due to error condition (see mdd_obd-project-MDT0000 log).
00000004:02000000:7.0:1340967117.856469:0:24346:0:(mdd_device.c:270:mdd_changelog_on()) mdd_obd-project-MDT0000: changelog on
00000004:00020000:7.0:1340967117.860651:0:24346:0:(mdd_device.c:274:mdd_changelog_on()) Changelogs cannot be enabled due to error condition (see mdd_obd-project-MDT0000 log).
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt; 
</comment>
                            <comment id="42033" author="ys" created="Fri, 20 Jul 2012 01:47:13 +0000"  >&lt;p&gt;Hi, Diego, Could you please upload the file MDT: CONFIGS/changelog_users for me? Juse use debugfs open your mdt device, and then use &apos;dump CONFIGS/changelog_users &amp;lt;choose a filename&amp;gt;&apos;. TIA.&lt;/p&gt;</comment>
                            <comment id="42641" author="dmoreno" created="Fri, 3 Aug 2012 03:53:27 +0000"  >&lt;p&gt;I attach the changelog_users and changelog_catalog files from the MDT not registering new readers.&lt;/p&gt;</comment>
                            <comment id="42657" author="ys" created="Fri, 3 Aug 2012 09:24:28 +0000"  >&lt;p&gt;Thanks, Diego, it is very helpful.&lt;/p&gt;</comment>
                            <comment id="102289" author="ys" created="Wed, 24 Dec 2014 09:23:27 +0000"  >&lt;p&gt;Hi, Diego, Is this issue still make sense? I am not reproduce it in my local box.&lt;/p&gt;</comment>
                            <comment id="102622" author="dmoreno" created="Tue, 6 Jan 2015 11:31:35 +0000"  >&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;We&apos;ve not seen this bug for a while.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                                        </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="11753" name="changelog_files.tgz" size="1164" author="dmoreno" created="Fri, 3 Aug 2012 03:53:27 +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|hzv3dr:</customfieldvalue>

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