<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:40:54 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>[LUDOC-183] Where to run changelog commands. </title>
                <link>https://jira.whamcloud.com/browse/LUDOC-183</link>
                <project id="10070" key="LUDOC">Lustre Documentation</project>
                    <description>&lt;p&gt;There was a conversation on HPDD-discuss recently about where to run certain changelog commands. The manual isn&apos;t clear on where certain commands have to be run, i.e. on client only, server only, etc. We need to clarify where changelog commands need to be run. &lt;/p&gt;

&lt;p&gt;The following is some of the conversation from the mail list:&lt;br/&gt;
Message 1:&lt;br/&gt;
In a test Lustre 2.4.0 filesystem we are running into difficulties viewing the changelogs on the mds.  Is there something I&apos;m doing wrong here? There are two clients registered, and I can see the current index increment when I perform file creates/unlinks.&lt;/p&gt;

&lt;p&gt;Any help would be greatly appreciated!&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@node-mds1 ~&amp;#93;&lt;/span&gt;# lfs changelog lustre-MDT0000 can&apos;t find fs root for &apos;(null)&apos;: -19 Can&apos;t open lustre-MDT0000: -19&lt;/p&gt;

&lt;p&gt;Can&apos;t start changelog: No such device&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@node-mds1 ~&amp;#93;&lt;/span&gt;# cat /proc/fs/lustre/mdd/lustre-MDT0000/changelog_users&lt;br/&gt;
current index: 120819&lt;br/&gt;
ID    index&lt;br/&gt;
cl1   2962&lt;br/&gt;
cl2   2962&lt;/p&gt;

&lt;p&gt;Message 2:&lt;br/&gt;
Does this command need to be run on the client instead of the server?  The manual doesn&apos;t make it very clear, but some of the examples I have seen show &quot;lfs changelog&quot; running on a system that is not the MDS.&lt;/p&gt;

&lt;p&gt;Message 3:&lt;br/&gt;
This is correct. You also should add the changelog consumer I&apos;d to your LFS&lt;br/&gt;
changelog command.&lt;/p&gt;

&lt;p&gt;Message 4:&lt;br/&gt;
Ah, that&apos;s it. &apos;lfs changelog lustre-MDT00000 cl1&apos; works from the client.&lt;/p&gt;</description>
                <environment></environment>
        <key id="20940">LUDOC-183</key>
            <summary>Where to run changelog commands. </summary>
                <type id="4" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="1" iconUrl="https://jira.whamcloud.com/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="LM-Triage">Lustre Manual Triage</assignee>
                                    <reporter username="jamesanunez">James Nunez</reporter>
                        <labels>
                    </labels>
                <created>Thu, 12 Sep 2013 22:36:28 +0000</created>
                <updated>Thu, 15 Sep 2016 14:44:06 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                    <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|hzw26f:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>10434</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>