<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:11:27 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-896] change e2fsprogs to make it allow directories over 2GB</title>
                <link>https://jira.whamcloud.com/browse/LU-896</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Parallel Directory Operation patch (&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-50&quot; title=&quot;pdirops patch for ldiskfs&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-50&quot;&gt;&lt;del&gt;LU-50&lt;/del&gt;&lt;/a&gt;, &lt;a href=&quot;http://review.whamcloud.com/#change,375&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#change,375&lt;/a&gt;) will support 3-level directory which requires directory size over 2G, besides code change for htree of ext4/ldiskfs, we also need to use i_size_high to store size of directory. This requires change to e2fsprogs to make it understand it.&lt;br/&gt;
We&apos;ve added feature EXT4_FEATURE_RO_COMPAT_LARGEDIR to ldiskfs to prevent kernel/e2fsprogs that only support 2-level to modify 3-level directories, this should also be added to e2fsprogs.&lt;/p&gt;</description>
                <environment></environment>
        <key id="12593">LU-896</key>
            <summary>change e2fsprogs to make it allow directories over 2GB</summary>
                <type id="4" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11310&amp;avatarType=issuetype">Improvement</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="liang">Liang Zhen</reporter>
                        <labels>
                            <label>e2fsprogs</label>
                    </labels>
                <created>Sun, 4 Dec 2011 10:45:29 +0000</created>
                <updated>Sat, 10 Sep 2016 08:14:08 +0000</updated>
                            <resolved>Sat, 10 Sep 2016 08:14:08 +0000</resolved>
                                    <version>Lustre 2.2.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="23668" author="adilger" created="Sun, 4 Dec 2011 13:03:47 +0000"  >&lt;p&gt;I was thinking about this further. It seems that this needs to be an INCOMPAT feature. The reason is that the old code used only frame-&amp;gt;at&lt;span class=&quot;error&quot;&gt;&amp;#91;2&amp;#93;&lt;/span&gt; to do tree traversal. This prevents the old code from even trying to access a 3-level tree I think, so RO_COMPAT is not enough in this case&lt;/p&gt;

&lt;p&gt;That said I guess that this feature as described is only for 2GB directories, but I don&apos;t know if that is useful without 3-level htree, so I&apos;m not sure if it is worthwhile to have two separate features?&lt;/p&gt;</comment>
                            <comment id="27973" author="adilger" created="Mon, 6 Feb 2012 13:46:07 +0000"  >&lt;p&gt;The kernel patch checks for INCOMPAT_LARGEDIR before using directories over 2GB or with more than 2-level htree.  This means the 2.2 ldiskfs is safe to use even without this patch in e2fsprogs, because nothing should be able to set INCOMPAT_LARGEDIR until e2fsprogs is updated.  This will also give us compatibility with 2.3 if the LARGEDIR feature can be enabled with newer e2fsprogs, but Lustre needs to be downgraded for some reason.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="14248">LU-1365</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="10289">LU-50</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="27930">LU-6030</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|hzw01j:</customfieldvalue>

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