<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:57:19 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-12978] FSTYPE=zfs ./lustre/tests/llmount.sh Fails with &quot;mount.lustre: lustre-mdt1/mdt1 has not been formatted with mkfs.lustre or the backend filesystem type is not supported by this tool&quot;</title>
                <link>https://jira.whamcloud.com/browse/LU-12978</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Running llmount.sh with FSTYPE=zfs fails with &quot;mount.lustre: lustre-mdt1/mdt1 has not been formatted with mkfs.lustre or the backend filesystem type is not supported by this tool&quot;.&lt;/p&gt;

&lt;p&gt;This was seen while working on &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3606&quot; title=&quot;Implement fallocate() support for ldiskfs Lustre&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3606&quot;&gt;&lt;del&gt;LU-3606&lt;/del&gt;&lt;/a&gt; (ZFS). The goal is to create a very small working ZFS instance for dev purpose. This is combined MDT/MGS. Changing test-framework.sh to using mount.lustre binary worked for me. This may just not be a bug. I am raising it to understand if this is really a bug or something to do with my environment. What are the difference of passing -t lustre vs using mount.lustre. I thought they ultimately boils down to same.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;This fails&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;
# FSTYPE=zfs bash ./lustre/tests/llmount.sh
Stopping clients: mrpel7 /mnt/lustre (opts:-f)
Stopping clients: mrpel7 /mnt/lustre2 (opts:-f)
mrpel7: executing set_hostid
Loading modules from /root/mrp/lustre-xx-3.10/lustre-release/lustre/tests/..
detected 2 online CPUs by sysfs
Force libcfs to create 2 CPU partitions
../lnet/lnet/lnet options: &lt;span class=&quot;code-quote&quot;&gt;&apos;networks=tcp0(eth1) accept=all&apos;&lt;/span&gt;
quota/lquota options: &lt;span class=&quot;code-quote&quot;&gt;&apos;hash_lqs_cur_bits=3&apos;&lt;/span&gt;
Formatting mgs, mds, osts
Format mds1: lustre-mdt1/mdt1
Format ost1: lustre-ost1/ost1
Format ost2: lustre-ost2/ost2
Checking servers environments
Checking clients mrpel7 environments
Loading modules from /root/mrp/lustre-xx-3.10/lustre-release/lustre/tests/..
detected 2 online CPUs by sysfs
Force libcfs to create 2 CPU partitions
Setup mgs, mdt, osts
Starting mds1: lustre-mdt1/mdt1 /mnt/lustre-mds1
mount.lustre: lustre-mdt1/mdt1 has not been formatted with mkfs.lustre or the backend filesystem type is not supported by &lt;span class=&quot;code-keyword&quot;&gt;this&lt;/span&gt; tool&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;This was fix by changing test-framework.sh&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;
diff --git a/lustre/tests/test-framework.sh b/lustre/tests/test-framework.sh
index 31e7ec3..a363fbb 100755
--- a/lustre/tests/test-framework.sh
+++ b/lustre/tests/test-framework.sh
@@ -2003,8 +2003,12 @@ mount_facet() {
 &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; [ -f $TMP/test-lu482-trigger ]; then
 RC=2
 &lt;span class=&quot;code-keyword&quot;&gt;else&lt;/span&gt;
+ #do_facet ${facet} \
+ # &lt;span class=&quot;code-quote&quot;&gt;&quot;mkdir -p $mntpt; $MOUNT_CMD $opts $dm_dev $mntpt&quot;&lt;/span&gt;
+ local ML_CMD=/usr/sbin/mount.lustre
 do_facet ${facet} \
- &lt;span class=&quot;code-quote&quot;&gt;&quot;mkdir -p $mntpt; $MOUNT_CMD $opts $dm_dev $mntpt&quot;&lt;/span&gt;
+ &lt;span class=&quot;code-quote&quot;&gt;&quot;mkdir -p $mntpt; $ML_CMD $opts $dm_dev $mntpt&quot;&lt;/span&gt;
 RC=${PIPESTATUS[0]}
 fi&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;Essentially changing from using &lt;b&gt;mount -t lustre&lt;/b&gt; to using &lt;b&gt;mount.lustre&lt;/b&gt; binary makes it work.&lt;/p&gt;

&lt;p&gt;My e2fsprogs version&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;
# rpm -qa | grep e2fsprogs-1
e2fsprogs-1.45.2.wc1-0.el7.x86_64&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;My setup and compile lustre&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;
# sh ./autogen.sh
# ./configure --enable-client --enable-server --disable-ldiskfs --with-linux=/usr/src/kernels/3.10.0-862.9.1.el7_lustre.x86_64/ --with-zfs=/root/zfs/zfs/zfs-0.7.12/ --with-spl=/root/zfs/spl/spl-0.7.12/
# make -j2
# make install&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;




&lt;p&gt;&#160;&lt;/p&gt;</description>
                <environment>FSTYPE=zfs&lt;br/&gt;
Singe Node Client/Server&lt;br/&gt;
Combined MDT/MGS</environment>
        <key id="57403">LU-12978</key>
            <summary>FSTYPE=zfs ./lustre/tests/llmount.sh Fails with &quot;mount.lustre: lustre-mdt1/mdt1 has not been formatted with mkfs.lustre or the backend filesystem type is not supported by this tool&quot;</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</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="6">Not a Bug</resolution>
                                        <assignee username="adilger">Andreas Dilger</assignee>
                                    <reporter username="arshad512">Arshad Hussain</reporter>
                        <labels>
                            <label>zfs</label>
                    </labels>
                <created>Sat, 16 Nov 2019 13:49:57 +0000</created>
                <updated>Sun, 17 Nov 2019 06:08:45 +0000</updated>
                            <resolved>Sun, 17 Nov 2019 06:08:45 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="258432" author="adilger" created="Sat, 16 Nov 2019 22:30:52 +0000"  >&lt;p&gt;Arshad, this is probably because &quot;&lt;tt&gt;mount -t lustre&lt;/tt&gt;&quot; is looking for the binary &quot;&lt;tt&gt;/sbin/mount.lustre&lt;/tt&gt;&quot; and if that is not found then it doesn&apos;t know how to mount the &quot;&lt;tt&gt;lustre&lt;/tt&gt;&quot; filesystem type.  Normally the test-framework.sh scripts will create a bind mount from &quot;&lt;tt&gt;$LUSTRE/lustre/utils/mount.lustre&lt;/tt&gt;&quot; to &quot;&lt;tt&gt;/sbin/mount.lustre&lt;/tt&gt;&quot; so that this works.  On rare occasions this can become incorrect (e.g. building and running from two different Lustre build directories, or if the options changed from the previous build of Lustre), so the old bind mount must be unmounted manually and restarted.&lt;/p&gt;</comment>
                            <comment id="258434" author="arshad512" created="Sun, 17 Nov 2019 06:07:45 +0000"  >&lt;p&gt;Andreas, Thanks!!&lt;/p&gt;

&lt;p&gt;I get it now.&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|i00pkn:</customfieldvalue>

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