<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:21:18 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-1974] File corruptions when running with LU-1442 patch, LU-1703 patch is also required.</title>
                <link>https://jira.whamcloud.com/browse/LU-1974</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;This bug is mainly open for information and to let the community aware, just in case ...&lt;/p&gt;

&lt;p&gt;So, here is the story, running with our/Bull Lustre 2.1.2 version, customer started to report files corruptions where a Client can successfully create/write/re-read files until an other Client tries to access the same file. At this time the files content became corrupted for all (missing blocks of data or z&#233;ro file-size ...) !!&lt;/p&gt;

&lt;p&gt;On the other hand, the corruptions have been identified to occur only on OSTs/OSCs where the file-creator Client had no more grant (&quot;/proc/fs/lustre/osc/&amp;lt;OST-import&amp;gt;/cur_&lt;/p&gt;
{dirty|grant|lost_grant}
&lt;p&gt;_bytes&quot; are Null) and also they seem to never be automatically recovered but only when we run a small program doing O_DIRECT writes to these OSTs ...&lt;/p&gt;

&lt;p&gt;Finally doing a full Lustre-trace of a program/command on a Client writing to these &quot;zero-grant&quot; OSTs, we found that the -EDQUOT was coming up during the cached-write standard path/routines and then the direct-IO path was attempted but ended with -EALREADY finally substitued with a successfull Null/0 return-value and no page written/flushed to the Server at all nor new grants recovered !!!&lt;/p&gt;

&lt;p&gt;Having a look to the concerned source-code, this would only occur if the written page(s) was not set Dirty ...&lt;/p&gt;

&lt;p&gt;Finally we found that this behavior/bug (missing &quot;set_page_dirty()&quot; vvp_io_commit_write() in case of -EDQUOT return from cl_page_add_cache() and implicit switch to direct-IO path/vvp_page_sync_io()) was not in Lustre v2.1.2 Base but has been introduced by patch from &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1442&quot; title=&quot;File corrupt with 1MiB-aligned 4k regions of zeros&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1442&quot;&gt;&lt;del&gt;LU-1442&lt;/del&gt;&lt;/a&gt; that our R&amp;amp;D included due to its high-level critical ... &lt;/p&gt;

&lt;p&gt;This bug has been since fixed by &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1703&quot; title=&quot;b2_1 can&amp;#39;t pass acc-sm test&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1703&quot;&gt;&lt;del&gt;LU-1703&lt;/del&gt;&lt;/a&gt; that we (I mean Bull R&amp;amp;D) need to integrate asap !!!!&lt;/p&gt;

&lt;p&gt;Also, I think that an explicit link/comment has to be added in &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1442&quot; title=&quot;File corrupt with 1MiB-aligned 4k regions of zeros&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1442&quot;&gt;&lt;del&gt;LU-1442&lt;/del&gt;&lt;/a&gt; to detail its running-dependency with &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1703&quot; title=&quot;b2_1 can&amp;#39;t pass acc-sm test&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1703&quot;&gt;&lt;del&gt;LU-1703&lt;/del&gt;&lt;/a&gt; patch.&lt;/p&gt;</description>
                <environment></environment>
        <key id="16030">LU-1974</key>
            <summary>File corruptions when running with LU-1442 patch, LU-1703 patch is also required.</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</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="1">Fixed</resolution>
                                        <assignee username="jay">Jinshan Xiong</assignee>
                                    <reporter username="louveta">Alexandre Louvet</reporter>
                        <labels>
                    </labels>
                <created>Tue, 18 Sep 2012 10:31:49 +0000</created>
                <updated>Mon, 19 Nov 2012 17:13:34 +0000</updated>
                            <resolved>Wed, 19 Sep 2012 08:11:51 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="45147" author="jay" created="Tue, 18 Sep 2012 12:11:30 +0000"  >&lt;p&gt;glad you have found the root cause.&lt;/p&gt;</comment>
                            <comment id="45154" author="pjones" created="Tue, 18 Sep 2012 12:57:10 +0000"  >&lt;p&gt;Thanks Bruno. I have added a link between the tickets. Both of these fixes are included in 2.1.3 so hopefully this is not a widespread issue. Do you need any further action or can we close this ticket?&lt;/p&gt;</comment>
                            <comment id="45200" author="bfaccini" created="Wed, 19 Sep 2012 02:07:08 +0000"  >&lt;p&gt;Yes, for sure ticket can be closed, I don&apos;t there are anything else to be done.&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|hzvghj:</customfieldvalue>

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