<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:37:16 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-3830] mount fails on targets configured with multiple mgs nids</title>
                <link>https://jira.whamcloud.com/browse/LU-3830</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;When a target is configured with multiple nids, the mount fails due to invalid mount options.&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;# mkfs.lustre --mgs --fsname=localfs /dev/ram0
# mkfs.lustre --mdt --fsname=localfs --mgsnode=30.1.0.95@o2ib0 --index=0 /dev/ram1
# mkfs.lustre --ost --fsname=localfs --mgsnode=30.1.0.95@o2ib0 --index=0 /dev/ram2
# mkfs.lustre --ost --fsname=localfs --mgsnode=30.1.0.95@o2ib0,30.2.0.95@o2ib1 --index=1 /dev/ram3

# mount.lustre /dev/ram0 /mnt/localfs/mgt
# mount.lustre /dev/ram1 /mnt/localfs/mdt
# mount.lustre /dev/ram2 /mnt/localfs/ost0
# mount.lustre /dev/ram3 /mnt/localfs/ost1
mount.lustre: mount /dev/ram3 at /mnt/localfs/ost1 failed: Invalid argument
This may have multiple causes.
Are the mount options correct?
Check the syslog for more info.

# mount.lustre /dev/ram3 /mnt/localfs/ost1 -v
arg[0] = /sbin/mount.lustre.orig
arg[1] = -v
arg[2] = /dev/ram3
arg[3] = /mnt/localfs/ost1
source = /dev/ram3 (/dev/ram3), target = /mnt/localfs/ost1
options = 
checking for existing Lustre data: found
Reading CONFIGS/mountdata
mounting device /dev/ram3 at /mnt/localfs/ost1, flags=0x1000000 options=osd=osd-ldiskfs,errors=remount-ro,mgsnode=30.1.0.95@o2ib,30.2.0.95@o2ib1,virgin,param=mgsnode=30.1.0.95@o2ib,30.2.0.95@o2ib1,svname=localfs-OST0001,device=/dev/ram3
mount.lustre: mount /dev/ram3 at /mnt/localfs/ost1 failed: Invalid argument retries left: 0
mount.lustre: mount /dev/ram3 at /mnt/localfs/ost1 failed: Invalid argument
This may have multiple causes.
Are the mount options correct?
Check the syslog for more info.

# tail -n 6 /var/log/syslog
1377250637 2013 Aug 23 11:37:17 mo95 kern err kernel LDISKFS-fs (ram3): Unrecognized mount option &quot;30.2.0.95@o2ib1&quot; or missing value
1377250637 2013 Aug 23 11:37:17 mo95 kern err kernel LustreError: 32322:0:(osd_handler.c:5349:osd_mount()) localfs-OST0001-osd: can&apos;t mount /dev/ram3: -22
1377250637 2013 Aug 23 11:37:17 mo95 kern err kernel LustreError: 32322:0:(obd_config.c:572:class_setup()) setup localfs-OST0001-osd failed (-22)
1377250637 2013 Aug 23 11:37:17 mo95 kern err kernel LustreError: 32322:0:(obd_mount.c:201:lustre_start_simple()) localfs-OST0001-osd setup error -22
1377250637 2013 Aug 23 11:37:17 mo95 kern err kernel LustreError: 32322:0:(obd_mount_server.c:1665:server_fill_super()) Unable to start osd on /dev/ram3: -22
1377250637 2013 Aug 23 11:37:17 mo95 kern err kernel LustreError: 32322:0:(obd_mount.c:1267:lustre_fill_super()) Unable to mount  (-22)

&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;It seems that mountdata options are now passed to mount.lustre as additional options.&lt;/p&gt;

&lt;p&gt;Unfortunately comma is used as a separator of mount options and multiple mgs nids are also separated by a comma.&lt;/p&gt;

&lt;p&gt;This lead to have the second mgs nid &quot;30.2.0.95@o2ib1&quot; to be processed as a mount option, which fails&lt;/p&gt;</description>
                <environment></environment>
        <key id="20590">LU-3830</key>
            <summary>mount fails on targets configured with multiple mgs nids</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="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="3">Duplicate</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="pichong">Gregoire Pichon</reporter>
                        <labels>
                    </labels>
                <created>Fri, 23 Aug 2013 09:43:56 +0000</created>
                <updated>Fri, 23 Aug 2013 12:24:34 +0000</updated>
                            <resolved>Fri, 23 Aug 2013 12:24:34 +0000</resolved>
                                    <version>Lustre 2.4.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="64943" author="niu" created="Fri, 23 Aug 2013 10:17:04 +0000"  >&lt;p&gt;It should have been fixed in &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3445&quot; title=&quot;Specifying multiple networks in NIDs does no longer work&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3445&quot;&gt;&lt;del&gt;LU-3445&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="64944" author="bfaccini" created="Fri, 23 Aug 2013 10:31:03 +0000"  >&lt;p&gt;Yes, Niu you have been too fast and I definitely agree! Gregoire, can you give a try to changes/fixes for &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3445&quot; title=&quot;Specifying multiple networks in NIDs does no longer work&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3445&quot;&gt;&lt;del&gt;LU-3445&lt;/del&gt;&lt;/a&gt; ??&lt;/p&gt;</comment>
                            <comment id="64945" author="pichong" created="Fri, 23 Aug 2013 12:08:56 +0000"  >&lt;p&gt;Thanks for the notice. I missed it when looking for existing Jira tickets.&lt;br/&gt;
This is definitively fixed by &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3445&quot; title=&quot;Specifying multiple networks in NIDs does no longer work&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3445&quot;&gt;&lt;del&gt;LU-3445&lt;/del&gt;&lt;/a&gt;.&lt;br/&gt;
Ticket can be closed.&lt;/p&gt;</comment>
                            <comment id="64946" author="bfaccini" created="Fri, 23 Aug 2013 12:24:34 +0000"  >&lt;p&gt;Ticket is a duplicate of &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3445&quot; title=&quot;Specifying multiple networks in NIDs does no longer work&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3445&quot;&gt;&lt;del&gt;LU-3445&lt;/del&gt;&lt;/a&gt; which is already fixed.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="19321">LU-3445</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </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_10040" key="com.atlassian.jira.plugin.system.customfieldtypes:labels">
                        <customfieldname>Epic</customfieldname>
                        <customfieldvalues>
                                        <label>mount</label>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzvz33:</customfieldvalue>

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