<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:41:13 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-223] Is the &quot;FID-in-dirent&quot; feature (ie. tunefs -O dirdata) is backwards compatible with 1.8.9 clients?</title>
                <link>https://jira.whamcloud.com/browse/LUDOC-223</link>
                <project id="10070" key="LUDOC">Lustre Documentation</project>
                    <description>&lt;p&gt;Yale just recently upgrade their MDS and OSS servers running 2.1.5 (upgraded from 1.8.9). However, the client are still running 1.8.9.&lt;/p&gt;

&lt;p&gt;Although it has been stated 1.6+ clients understand the new FID format, the 2.x lustre operations manual at hpdd-intel doesn&apos;t &lt;b&gt;explicitly&lt;/b&gt; say it will work with older clients.  They would like clarification on if the &quot;FID-in-dirent&quot; feature (ie. tunefs -O dirdata) is backwards compatible with 1.8.9 clients ?&lt;/p&gt;

&lt;p&gt;Also, is there high risk involved enabling &quot;dirdata&quot; when running old 1.8.9 clients ?  Any opinions if there is benefit in using this flag ?&lt;/p&gt;

</description>
                <environment>Lustre 2.1.5 MDS/OSS&lt;br/&gt;
Lustre 1.8.9 Clients</environment>
        <key id="23041">LUDOC-223</key>
            <summary>Is the &quot;FID-in-dirent&quot; feature (ie. tunefs -O dirdata) is backwards compatible with 1.8.9 clients?</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="1">Fixed</resolution>
                                        <assignee username="jlevi">Jodi Levi</assignee>
                                    <reporter username="orentas">Oz Rentas</reporter>
                        <labels>
                    </labels>
                <created>Thu, 6 Feb 2014 21:49:11 +0000</created>
                <updated>Fri, 14 Mar 2014 01:31:15 +0000</updated>
                            <resolved>Fri, 14 Mar 2014 01:31:15 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="76429" author="ihara" created="Fri, 7 Feb 2014 03:52:43 +0000"  >&lt;p&gt;hmm.. Oz, I don&apos;t think this is Lustre Doc issue. we should change &quot;issue type&quot;..&lt;/p&gt;</comment>
                            <comment id="76727" author="orentas" created="Tue, 11 Feb 2014 15:38:54 +0000"  >&lt;p&gt;Andreas responded to this one on HDPP-discuss:&lt;/p&gt;

&lt;p&gt;The fid-in-dirent feature is only relevant on the MDT. It does not directly affect the client or OST, but will affect the performance that the client sees when accessing files created under 2.x. &lt;/p&gt;

&lt;p&gt;There is a noticeable performance improvement (or more specifically no performance degradation) for 2.x files with this feature enabled. The main reason it is not enabled by default is that it impacts the ability to downgrade to 1.8 again safely. Once you know you don&apos;t want to downgrade again it is ok to enable it. &lt;/p&gt;


&lt;p&gt;Please close ticket.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Oz&lt;/p&gt;</comment>
                            <comment id="79303" author="jfc" created="Fri, 14 Mar 2014 01:31:15 +0000"  >&lt;p&gt;Marked as resolved per partner&apos;s guidance.&lt;br/&gt;
~ jfc.&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|hzwegv:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>12561</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10021"><![CDATA[2]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>