<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:45:35 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-4755] ASSERTION( req-&gt;rq_reqbuf_len &gt;= msgsize ) failed when using 4MB RPC</title>
                <link>https://jira.whamcloud.com/browse/LU-4755</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;After ran &quot;lctl set_param osc.*.max_pages_per_rpc=4M&quot;, we ran 4k random write test with IOR and easily hit this problem.&lt;/p&gt;

&lt;p&gt;After some test, we found that the biggest value of msgsize is 16384 for bulk write, while req-&amp;gt;rq_reqbuf_len is only 8192.&lt;/p&gt;</description>
                <environment></environment>
        <key id="23601">LU-4755</key>
            <summary>ASSERTION( req-&gt;rq_reqbuf_len &gt;= msgsize ) failed when using 4MB RPC</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="1">Fixed</resolution>
                                        <assignee username="cliffw">Cliff White</assignee>
                                    <reporter username="lixi">Li Xi</reporter>
                        <labels>
                            <label>patch</label>
                    </labels>
                <created>Wed, 12 Mar 2014 11:23:18 +0000</created>
                <updated>Thu, 17 Sep 2015 23:17:51 +0000</updated>
                            <resolved>Wed, 16 Jul 2014 14:42:10 +0000</resolved>
                                                    <fixVersion>Lustre 2.7.0</fixVersion>
                    <fixVersion>Lustre 2.5.3</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>7</watches>
                                                                            <comments>
                            <comment id="79102" author="lixi" created="Wed, 12 Mar 2014 11:30:34 +0000"  >&lt;p&gt;With following patch, this problem won&apos;t be reproduced.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/9599&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/9599&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;However, I am wondering whether there is any automatic way to calculate the proper value of OST_MAXREQSIZE at compile time rather than doing guesswork or manual caculation.&lt;/p&gt;</comment>
                            <comment id="79382" author="pjones" created="Fri, 14 Mar 2014 22:35:33 +0000"  >&lt;p&gt;Cliff&lt;/p&gt;

&lt;p&gt;Could you please take care of this patch?&lt;/p&gt;

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

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="79975" author="adilger" created="Fri, 21 Mar 2014 10:22:29 +0000"  >&lt;p&gt;Actually, before I dismiss the patch to increase the request size, it is worthwhile to ask if there is any performance improvement from sending 4096 random pages in one RPC compared to 16 x 256 random pages in separate RPCs?  It might even be faster to send parallel RPCs due to checksums running on separate cores and being handled in parallel on the OST.  If there is no improvement from many random pages in one RPC, it is better to just limit the number of niobufs that the client sends in one RPC.&lt;/p&gt;</comment>
                            <comment id="87279" author="cliffw" created="Mon, 23 Jun 2014 15:56:10 +0000"  >&lt;p&gt;The patch is failing sanity test at this time. Is it possible to submit a new patch?&lt;/p&gt;</comment>
                            <comment id="89209" author="jlevi" created="Wed, 16 Jul 2014 14:42:10 +0000"  >&lt;p&gt;Patch landed to Master.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                                        </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="32205">LU-7181</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|hzwhhr:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>13084</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>