<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:36:44 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-3767] 32TB OST support in 1.8.9</title>
                <link>https://jira.whamcloud.com/browse/LU-3767</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;I understand that ldiskfs has not been extensively tested on LUNs over 24TB with lustre 1.8.x and el5.x and the force_over_24tb option is required to format a larger LUN. We would like to take advantage of 32TB LUNS from a RAID6 with 8x4TB drives if at all possible on a 1.8 branch. Has testing on larger OSTs been undertaken since &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-136&quot; title=&quot;test e2fsprogs-1.42.wc1 against 32TB+ ldiskfs filesystems&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-136&quot;&gt;&lt;del&gt;LU-136&lt;/del&gt;&lt;/a&gt;, which appeared to only test 128TB on the 2.1 code?  Are there any other issues that might prevent 32TB OSTs from working?&lt;/p&gt;</description>
                <environment>RHEL5.9, distribution provided ib stack</environment>
        <key id="20360">LU-3767</key>
            <summary>32TB OST support in 1.8.9</summary>
                <type id="2" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11311&amp;avatarType=issuetype">New Feature</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="4">Incomplete</resolution>
                                        <assignee username="jamesanunez">James Nunez</assignee>
                                    <reporter username="blakecaldwell">Blake Caldwell</reporter>
                        <labels>
                    </labels>
                <created>Thu, 15 Aug 2013 17:31:11 +0000</created>
                <updated>Sat, 14 Sep 2013 03:53:55 +0000</updated>
                            <resolved>Sat, 14 Sep 2013 03:53:54 +0000</resolved>
                                    <version>Lustre 1.8.9</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="64349" author="blakecaldwell" created="Thu, 15 Aug 2013 17:34:01 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-419&quot; title=&quot;Running 1.8.6WC the mkfs.lustre failed to format a 22.94TB LUN, Size of device too big to be expressed in 32 bits using a block size of 4096 &quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-419&quot;&gt;&lt;del&gt;LU-419&lt;/del&gt;&lt;/a&gt; enabled the 64-bit feature to allow formatting LUNS larger than 16TB and was landed in 1.8.7&lt;/p&gt;</comment>
                            <comment id="64351" author="pjones" created="Thu, 15 Aug 2013 17:52:43 +0000"  >&lt;p&gt;James&lt;/p&gt;

&lt;p&gt;Please can you help with this one?&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="64354" author="jamesanunez" created="Thu, 15 Aug 2013 18:15:58 +0000"  >&lt;p&gt;Blake, &lt;br/&gt;
I&apos;m looking into if there are any issues with 32TB OST in 1.8.9. &lt;/p&gt;

&lt;p&gt;By the way, what version of e2fsprogs are you using?&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
James&lt;/p&gt;</comment>
                            <comment id="64355" author="blakecaldwell" created="Thu, 15 Aug 2013 18:20:31 +0000"  >&lt;p&gt;e2fsprogs-1.42.3.wc3-0redhat&lt;/p&gt;

&lt;p&gt;and 2.6.18-348.3.1.el5 kernel&lt;/p&gt;</comment>
                            <comment id="64366" author="jamesanunez" created="Thu, 15 Aug 2013 21:05:33 +0000"  >&lt;p&gt;Thanks for the info, Blake. &lt;/p&gt;

&lt;p&gt;I&apos;m just trying to find out if there was a technical reason why the patch for b1_8 &lt;a href=&quot;http://review.whamcloud.com/#/c/589/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/589/&lt;/a&gt; only increased the max OST size from 16 TB to 24TB and not larger. &lt;/p&gt;</comment>
                            <comment id="64396" author="jamesanunez" created="Fri, 16 Aug 2013 13:46:31 +0000"  >&lt;p&gt;Prior to landing &lt;a href=&quot;http://review.whamcloud.com/#/c/589/1&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/589/1&lt;/a&gt;, format and mount of 128TB LUNs with 1.8.6 were successful using the &quot;force_over_16tb&quot; flag. Only a partial test, llverdev and llverfs, was run on the 128TB LUNs. Full tests were not run.&lt;/p&gt;

&lt;p&gt;Officially, we&apos;ve only tested and support up to 24TB LUNs for 1.8.x, but it looks like it just may work. &lt;/p&gt;</comment>
                            <comment id="66673" author="jamesanunez" created="Sat, 14 Sep 2013 03:53:55 +0000"  >&lt;p&gt;ORNL has decided to not test/create 32TB LUNs for use with their 1.8 file systems. Thus we are closing this ticket since the testing is no longer needed. &lt;/p&gt;

&lt;p&gt;Please reopen this ticket if there is a desire to put 32 TB LUNs into production. &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|hzvy1z:</customfieldvalue>

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