<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:22:10 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-8974] &#1057;hange force_over_256tb lustre mount option to force_over_512tb for ldiskfs</title>
                <link>https://jira.whamcloud.com/browse/LU-8974</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Currently attempts of creating ldisk file system with size &amp;gt;256TB finished with message.&lt;br/&gt;
&quot;LDISKFS-fs does not support file systems greater than 256TB and can cause data corruption.Use &quot;force_over_256tb&quot; mount option to override.&quot;&lt;br/&gt;
Before using &quot;force_over_256tb&quot; parameter in production systems lustre file system software should be analyzed to point possible large disks support issues. This issue is about research of some aspects of Lustre software. Finally patch that change &quot;force_over_256tb&quot; to &quot;force_over_512tb&quot; should be landed. This gives ability use ldiskfs partitions &amp;lt;512tb without options.&lt;/p&gt;</description>
                <environment></environment>
        <key id="42652">LU-8974</key>
            <summary>&#1057;hange force_over_256tb lustre mount option to force_over_512tb for ldiskfs</summary>
                <type id="4" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11310&amp;avatarType=issuetype">Improvement</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="1">Fixed</resolution>
                                        <assignee username="adilger">Andreas Dilger</assignee>
                                    <reporter username="artem_blagodarenko">Artem Blagodarenko</reporter>
                        <labels>
                    </labels>
                <created>Mon, 26 Dec 2016 07:10:18 +0000</created>
                <updated>Fri, 8 Nov 2019 03:06:46 +0000</updated>
                            <resolved>Tue, 18 Apr 2017 17:44:56 +0000</resolved>
                                                    <fixVersion>Lustre 2.10.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="179036" author="gerrit" created="Mon, 26 Dec 2016 10:01:56 +0000"  >&lt;p&gt;Artem Blagodarenko (artem.blagodarenko@seagate.com) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/24524&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/24524&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-8974&quot; title=&quot;&#1057;hange force_over_256tb lustre mount option to force_over_512tb for ldiskfs&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-8974&quot;&gt;&lt;del&gt;LU-8974&lt;/del&gt;&lt;/a&gt; osd-ldiskfs: increase supported ldiskfs fs size&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: b203e05a88d6c02b7f655598aacabfeb946aed66&lt;/p&gt;</comment>
                            <comment id="179049" author="artem_blagodarenko" created="Mon, 26 Dec 2016 14:21:12 +0000"  >&lt;p&gt;Some researched aspects &lt;/p&gt;

&lt;p&gt;&lt;b&gt;META_BG&lt;/b&gt;&lt;br/&gt;
(required)&lt;br/&gt;
Without the option META_BG, for safety concerns, all block group descriptors copies are kept in the first block group. Given the default 128MiB(2^27 bytes) block group size and 64-byte group descriptors, ext4 can have at most 2^27/64 = 2^21 block groups. This limits the entire filesystem size to 2^21 &#8727; 2^27 = 2^48 bytes or 256TiB.&lt;br/&gt;
The solution to this problem is to use the metablock group feature (META_BG), which is already in ext3 for all 2.6 releases. Some issues found during testing&lt;br/&gt;
 &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-8443&quot; title=&quot;Can&amp;#39;t create Lustre FS with enabled meta_bg option&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-8443&quot;&gt;&lt;del&gt;LU-8443&lt;/del&gt;&lt;/a&gt; &quot;Can&apos;t create Lustre FS with enabled meta_bg option&quot;. Patch is landed.&lt;br/&gt;
 &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-8976&quot; title=&quot;Apply patch &amp;quot;libext2fs: fix maximum bg overhead calculation with meta_bg enabled&amp;quot;&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-8976&quot;&gt;&lt;del&gt;LU-8976&lt;/del&gt;&lt;/a&gt; &quot;Cannot create filesystem with requested number of inodes while setting up superblock&quot; Patch from upstream must be cherrypicked to solve the issue.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;large dir&lt;/b&gt;&lt;br/&gt;
(useful in case of many files in the directory)&lt;br/&gt;
&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1365&quot; title=&quot;Implement ldiskfs LARGEDIR support for e2fsprogs&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1365&quot;&gt;&lt;del&gt;LU-1365&lt;/del&gt;&lt;/a&gt; &quot;Implement ldiskfs LARGEDIR support for e2fsprogs&quot;  Sending upstream.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;xattr external inode referance&lt;/b&gt;&lt;br/&gt;
(tested, landing for regression testing)&lt;br/&gt;
&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-8444&quot; title=&quot;Add test for LU-7325 patch&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-8444&quot;&gt;&lt;del&gt;LU-8444&lt;/del&gt;&lt;/a&gt; the patch from &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7325&quot; title=&quot;wrong integer type used for inode number in LargeEA patch&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7325&quot;&gt;&lt;del&gt;LU-7325&lt;/del&gt;&lt;/a&gt; fixes this issue: &quot;Hitting &quot;LDISKFS-fs error (device md66): ldiskfs_xattr_inode_iget: error while reading EA inode -2147483347&quot; Inspection&lt;/p&gt;


</comment>
                            <comment id="184288" author="gerrit" created="Fri, 10 Feb 2017 03:51:42 +0000"  >&lt;p&gt;Oleg Drokin (oleg.drokin@intel.com) merged in patch &lt;a href=&quot;https://review.whamcloud.com/24524/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/24524/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-8974&quot; title=&quot;&#1057;hange force_over_256tb lustre mount option to force_over_512tb for ldiskfs&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-8974&quot;&gt;&lt;del&gt;LU-8974&lt;/del&gt;&lt;/a&gt; osd-ldiskfs: increase supported ldiskfs fs size&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: cfa981f3bf06d602aee998e64d4758e13f48aab8&lt;/p&gt;</comment>
                            <comment id="192547" author="adilger" created="Tue, 18 Apr 2017 17:44:56 +0000"  >&lt;p&gt;Patch landed to 2.10.&lt;/p&gt;</comment>
                            <comment id="257930" author="gerrit" created="Thu, 7 Nov 2019 15:58:02 +0000"  >&lt;p&gt;Artem Blagodarenko (c17828@cray.com) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/36705&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/36705&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-8974&quot; title=&quot;&#1057;hange force_over_256tb lustre mount option to force_over_512tb for ldiskfs&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-8974&quot;&gt;&lt;del&gt;LU-8974&lt;/del&gt;&lt;/a&gt; osd-ldiskfs: increase supported size to 1024tb&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: c87bbaf9063494f702c0d0b5884d11dba483e306&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                                        </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="38444">LU-8443</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="14248">LU-1365</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="57333">LU-12950</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="38446">LU-8444</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="42659">LU-8976</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="33812">LU-7592</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="38564">LU-8465</issuekey>
        </issuelink>
                            </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|hzyz9j:</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>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>