<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:41:34 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-268] Insert example MDS format cmd into Manual for multiple/failover nid - case</title>
                <link>https://jira.whamcloud.com/browse/LUDOC-268</link>
                <project id="10070" key="LUDOC">Lustre Documentation</project>
                    <description>&lt;p&gt;As of 2015-02-19, the Lustre 2.x manual lacks an explicti example of how to format MGS and MDT in case of&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;separate MGS and MDT and&lt;/li&gt;
	&lt;li&gt;failover pair of MDS where these two targets might be running&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;The proposed example is&lt;br/&gt;
&quot;mkfs.lustre  --mgs  --servicenode=mgsNID1 --servicenode=mgsNID2 /dev/mgs-disk&quot;&lt;/p&gt;

&lt;p&gt;&quot;mkfs.lustre --mdt --fsname=lustre --index=0 --servicenode=NID1 --servicenode=NID2 --mgsnode=mgsNID1 --mgsnode=mgsNID2 /dev/mdt-disk&quot;&lt;/p&gt;

&lt;p&gt;Possible placement: Section 13.10. Specifying NIDs and Failover&lt;/p&gt;

&lt;p&gt;The examples given there almost cover the case, but the given command for mds0 will not work for separate mgs and mdt partitions, since the --mgsnode specification is missing.&lt;br/&gt;
Giving instead only 2 --mgsnode= specifications defines only the failover nids for the MGS, not the ones for the MDT. Even if MGS and MDT are run always from the same machine, i.e. if &quot;mgsNID1&quot; and &quot;NID1&quot; from my example command are the same, failover does not work, unless this nid is also specified as a --servicenode&lt;/p&gt;

&lt;p&gt;Attentive reading of the manual might give the necessary clues right now, but seeing all options together in an example makes things by far easier.&lt;/p&gt;</description>
                <environment></environment>
        <key id="28761">LUDOC-268</key>
            <summary>Insert example MDS format cmd into Manual for multiple/failover nid - case</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="thomasr">Thomas Roth</reporter>
                        <labels>
                    </labels>
                <created>Thu, 19 Feb 2015 16:32:29 +0000</created>
                <updated>Thu, 15 Sep 2016 14:44:08 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="29534">LUDOC-274</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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|hzx6n3:</customfieldvalue>

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