<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:40:08 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-11007] Upgrading Lustre 2.8fe to 2.10.x - on-disk format change question</title>
                <link>https://jira.whamcloud.com/browse/LU-11007</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Are there on-disk format changes between Lustre 2.8fe and Lustre 2.10.x, even if one avoids use of new features to 2.10 like PFL and project quota, and avoids DNE2?&lt;/p&gt;

&lt;p&gt;IE if we were to mount a Lustre 2.8fe file system with Lustre 2.10 kernel modules, and perform some mdtests and IORs, would there be on-disk changes that prevent the file system from being mounted again with 2.8fe kernel modules?&lt;/p&gt;

&lt;p&gt;Is the answer different for ldiskfs than for ZFS backend?&lt;/p&gt;

&lt;p&gt;The context would be performing tests before releasing the file system to users, after upgrading the software from 2.8fe to 2.10.x., and falling back to 2.8fe if the tests reveal a problem.&lt;/p&gt;</description>
                <environment></environment>
        <key id="52153">LU-11007</key>
            <summary>Upgrading Lustre 2.8fe to 2.10.x - on-disk format change question</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="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="10000">Done</resolution>
                                        <assignee username="pjones">Peter Jones</assignee>
                                    <reporter username="ofaaland">Olaf Faaland</reporter>
                        <labels>
                            <label>llnl</label>
                    </labels>
                <created>Tue, 8 May 2018 17:51:57 +0000</created>
                <updated>Wed, 7 Nov 2018 17:56:36 +0000</updated>
                            <resolved>Wed, 7 Nov 2018 17:56:36 +0000</resolved>
                                    <version>Lustre 2.10.5</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="227521" author="ofaaland" created="Tue, 8 May 2018 17:53:31 +0000"  >&lt;p&gt;This would be a last resort, but it would be useful to know if it&apos;s even worth trying.  That&apos;s especially true with ldiskfs since we cannot create snapshots.&lt;/p&gt;</comment>
                            <comment id="227524" author="pjones" created="Tue, 8 May 2018 18:14:59 +0000"  >&lt;p&gt;Olaf&lt;/p&gt;

&lt;p&gt;While we have not tested this ourselves it seems possible that it would work. It seems quite likely that this will work fine for ZFS but we are less sure about ldiskfs so if you decide to explore this option you should focus your testing there.&lt;/p&gt;

&lt;p&gt;Regards&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="227537" author="adilger" created="Tue, 8 May 2018 20:30:28 +0000"  >&lt;p&gt;One possible issue is the addition of the ZFS native dnode quota accounting (which is a zpool feature that needs to be enabled explicitly), which is enabled with ZFS 0.7.0 and Lustre 2.10.  However, I don&apos;t think you use the Lustre dnode accounting because it was not working well before that update in any case.  Similarly, the &lt;tt&gt;multimount&lt;/tt&gt; feature is new in ZFS 0.7 and Lustre 2.10, but AFAIK you are already using ZFS 0.7, and it would need to be explicitly enabled in any case.&lt;/p&gt;

&lt;p&gt;If you don&apos;t use project quota, PFL layouts, or DNE-2 there shouldn&apos;t be any issues downgrading.  There is still an &quot;&lt;tt&gt;mdt.&amp;#42;.enable_remote_dir&lt;/tt&gt;&quot; tunable that controls whether DNE striped or remote directories can be created by regular users or not, but it controls both DNE-1 and DNE-2 directories.  There is &lt;b&gt;not&lt;/b&gt; a tunable to prevent the creation of PFL files if some user tried to do that, but that would only affect those specific files from being accessed if the system was downgraded again.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                                        </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|hzzwxb:</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>