<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:46:54 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-11784] PFL layouts can exceed EA size limits</title>
                <link>https://jira.whamcloud.com/browse/LU-11784</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;The current code for limiting layout sizes is not fully updated for PFL.&#160; In particular, some of the limits use&#160;LOV_MAX_STRIPE_COUNT and the size of a stripe to fix the maximum layout size.&#160; This breaks down with multiple components.&lt;/p&gt;

&lt;p&gt;The overstriping feature in &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-9846&quot; title=&quot;Overstriping - more than stripe per OST per component&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-9846&quot;&gt;&lt;del&gt;LU-9846&lt;/del&gt;&lt;/a&gt; makes it easy to reach high stripe counts, and so makes it more urgent to address this issue.&lt;/p&gt;

&lt;p&gt;This ticket is to work out what the actual current limit on EA size is (there are several different ones documented in the code, and Lustre crashes below all of them) and update the layout code to not allow creation of layouts that exceed it.&lt;/p&gt;</description>
                <environment></environment>
        <key id="54307">LU-11784</key>
            <summary>PFL layouts can exceed EA size limits</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="3">Duplicate</resolution>
                                        <assignee username="paf">Patrick Farrell</assignee>
                                    <reporter username="paf">Patrick Farrell</reporter>
                        <labels>
                            <label>PFL2</label>
                    </labels>
                <created>Fri, 14 Dec 2018 20:50:56 +0000</created>
                <updated>Sat, 7 Mar 2020 08:06:14 +0000</updated>
                            <resolved>Sat, 7 Mar 2020 08:06:14 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="250126" author="adilger" created="Thu, 27 Jun 2019 05:41:51 +0000"  >&lt;p&gt;Patrick, is this ticket still needed, or were the &quot;large xattr&quot; issues mostly addressed?  Are we sticking with the &quot;2000 stripe&quot; maximum (about 48KB for plain RAID-0 layouts), or do we want to bite the bullet and allow a layout that is closer to the 64KB xattr size limit (possibly reserving some space so that the whole MDS reply can still fit into a 64KB buffer)?&lt;/p&gt;

&lt;p&gt;That would give us closer to 2500-2600 stripes, maybe 2560 stripes = 61504 bytes reasonable maximum to shoot for, leaving 4032 bytes for other parts of the RPC.&lt;/p&gt;

&lt;p&gt;Not that this is an urgent issue to pay attention to, just trying to close the ticket if it isn&apos;t needed.&lt;/p&gt;</comment>
                            <comment id="264835" author="adilger" created="Sat, 7 Mar 2020 08:06:14 +0000"  >&lt;p&gt;I think this was resolved with &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-9846&quot; title=&quot;Overstriping - more than stripe per OST per component&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-9846&quot;&gt;&lt;del&gt;LU-9846&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="47710">LU-9846</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <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|i0083r:</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>