<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:33:39 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-3408] client-only &quot;make rpms&quot; ldiskfs detection inconsistent</title>
                <link>https://jira.whamcloud.com/browse/LU-3408</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;I tried to build a client-only RPM using in the Lustre source tree for patchless kernel 2.6.32.26-175.fc12.x86_64 using the standard:&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;sh autogen
./configure
make rpms
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;In previous releases, configure would correctly detect that ldiskfs was not available for the kernel and/or the kernel sources were not available and do a client-only build.&lt;/p&gt;

&lt;p&gt;Unfortunately, the 2.4.0 client build died in mid-stream due to inconsistent detection of ldiskfs support.  In the top-level configure.ac file it has:&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;# Overridden by --without-ldiskfs/--with-zfs configure options
AM_CONDITIONAL(LDISKFS_ENABLED, true)
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Which sets &lt;tt&gt;LDISKFS_ENABLED&lt;/tt&gt;, but later on in the build it failed in mount_utils.c with:&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;mount_lustre-mount_utils.o: In function `osd_is_lustre&apos;: 
/usr/src/lustre-head/lustre/utils/mount_utils.c:461: undefined reference to `ldiskfs_is_lustre&apos;          
mount_lustre-mount_utils.o: In function `osd_fini&apos;:
/usr/src/lustre-head/lustre/utils/mount_utils.c:650: undefined reference to `ldiskfs_fini&apos;          
mount_lustre-mount_utils.o: In function `osd_init&apos;:
/usr/src/lustre-head/lustre/utils/mount_utils.c:632: undefined reference to `ldiskfs_init&apos;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;This is in&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;&lt;span class=&quot;code-comment&quot;&gt;/* Was &lt;span class=&quot;code-keyword&quot;&gt;this&lt;/span&gt; device formatted &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; Lustre */&lt;/span&gt;
&lt;span class=&quot;code-object&quot;&gt;int&lt;/span&gt; osd_is_lustre(&lt;span class=&quot;code-object&quot;&gt;char&lt;/span&gt; *dev, unsigned *mount_type)
{
        vprint(&lt;span class=&quot;code-quote&quot;&gt;&quot;checking &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; existing Lustre data: &quot;&lt;/span&gt;);

#ifdef HAVE_LDISKFS_OSD
        &lt;span class=&quot;code-keyword&quot;&gt;if&lt;/span&gt; (ldiskfs_is_lustre(dev, mount_type)) {
                vprint(&lt;span class=&quot;code-quote&quot;&gt;&quot;found\n&quot;&lt;/span&gt;);
                &lt;span class=&quot;code-keyword&quot;&gt;return&lt;/span&gt; 1;
        }
#endif &lt;span class=&quot;code-comment&quot;&gt;/* HAVE_LDISKFS_OSD */&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Since &lt;tt&gt;HAVE_LDISKFS_OSD&lt;/tt&gt; is set, but &lt;tt&gt;mount_utils_ldiskfs.c&lt;/tt&gt; is not being built.  The ldiskfs configure step correctly detects no ldiskfs support for this kernel, and tries to disable ldiskfs and set &lt;tt&gt;-&lt;del&gt;disable-server&lt;/tt&gt;, but this is &quot;lost&quot; in the sub-configure step?  The ldiskfs configure &lt;em&gt;shouldn&apos;t&lt;/em&gt; set &lt;tt&gt;&lt;/del&gt;-disable-server&lt;/tt&gt; itself anyway, because it may be a ZFS-only server system.&lt;/p&gt;

&lt;p&gt;It would seem better to run the ldiskfs and ZFS configure stages early on in the configure process, then if no backing filesystem support is found, it should automatically set &lt;tt&gt;--disable-server&lt;/tt&gt; for the main Lustre build.&lt;/p&gt;</description>
                <environment>patchless client: 2.6.32.26-175.fc12.x86_64</environment>
        <key id="19170">LU-3408</key>
            <summary>client-only &quot;make rpms&quot; ldiskfs detection inconsistent</summary>
                <type id="7" iconUrl="https://jira.whamcloud.com/images/icons/issuetypes/task_agile.png">Technical task</type>
                            <parent id="13505">LU-1199</parent>
                                    <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="3">Duplicate</resolution>
                                        <assignee username="mdiep">Minh Diep</assignee>
                                    <reporter username="adilger">Andreas Dilger</reporter>
                        <labels>
                    </labels>
                <created>Tue, 28 May 2013 07:46:59 +0000</created>
                <updated>Mon, 16 Sep 2013 22:30:54 +0000</updated>
                            <resolved>Mon, 16 Sep 2013 22:30:54 +0000</resolved>
                                    <version>Lustre 2.4.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="59464" author="morrone" created="Tue, 28 May 2013 17:50:51 +0000"  >&lt;p&gt;We need to get rid of those static AM_CONDITIONAL declarations all together.  Honestly, I suspect that we just forgot that they were there.&lt;/p&gt;

&lt;p&gt;We have a dynamic declaration for ldiskfs here:&lt;/p&gt;

&lt;p&gt;   config/lustre-build-ldiskfs.m4:AM_CONDITIONAL(LDISKFS_ENABLED, test x$with_ldiskfs = xyes)&lt;/p&gt;

&lt;p&gt;and one for zfs here:&lt;/p&gt;

&lt;p&gt;   config/lustre-build-zfs.m4:     AM_CONDITIONAL(ZFS_ENABLED, test x$enable_zfs = xyes)&lt;/p&gt;

&lt;p&gt;Really, we are supposed to call AM_CONDITIONAL only one time for any given variable, so we&apos;re doing it wrong.  So we should drop the static declaration, then fix up the defaults and ordering to get what you are looking for.&lt;/p&gt;</comment>
                            <comment id="66789" author="jlevi" created="Mon, 16 Sep 2013 22:30:54 +0000"  >&lt;p&gt;Duplicate of &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3954&quot; title=&quot;client-only &amp;quot;make rpms&amp;quot; ldiskfs detection inconsistent&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3954&quot;&gt;&lt;del&gt;LU-3954&lt;/del&gt;&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="20970">LU-3954</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_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzvry7:</customfieldvalue>

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