<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:12:37 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-1010] lfsck.sh test: e2fsck_pass1:1402: increase inode 20 badness 0 to 1</title>
                <link>https://jira.whamcloud.com/browse/LU-1010</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;It appears that Lustre is creating somewhat invalid files on the OST:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://maloo.whamcloud.com/test_sets/cbcbbd2e-3f50-11e1-990e-5254004bbbd3&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://maloo.whamcloud.com/test_sets/cbcbbd2e-3f50-11e1-990e-5254004bbbd3&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;09:47:21:fat-intel-1vm4: e2fsck_pass1:1402: increase inode 20 badness 0 to 1&lt;br/&gt;
09:47:21:fat-intel-1vm4: e2fsck_pass1:1406: increase inode 20 badness 1 to 3&lt;br/&gt;
09:47:21:fat-intel-1vm4: e2fsck_pass1:1402: increase inode 31 badness 0 to 1&lt;br/&gt;
09:47:21:fat-intel-1vm4: e2fsck_pass1:1406: increase inode 31 badness 1 to 3&lt;br/&gt;
09:47:21:fat-intel-1vm4: e2fsck_pass1:1402: increase inode 32 badness 0 to 1&lt;br/&gt;
09:47:21:fat-intel-1vm4: e2fsck_pass1:1406: increase inode 32 badness 1 to 3&lt;/p&gt;

&lt;p&gt;These messages relate to the checks added in the &quot;e2fsprogs-ibadness-counter&quot; patch:&lt;/p&gt;

&lt;p&gt;               if (EXT4_XTIME_FUTURE(ctx, sb, inode-&amp;gt;i_atime,ctx-&amp;gt;time_fudge)||&lt;br/&gt;
                   EXT4_XTIME_FUTURE(ctx, sb, inode-&amp;gt;i_mtime,ctx-&amp;gt;time_fudge))&lt;br/&gt;
                       e2fsck_mark_inode_bad(ctx, ino, BADNESS_NORMAL);+&lt;br/&gt;
               if (EXT4_XTIME_FUTURE(ctx, sb, inode-&amp;gt;i_ctime,ctx-&amp;gt;time_fudge)||&lt;br/&gt;
                   EXT4_XTIME_ANCIENT(ctx, sb, inode-&amp;gt;i_ctime,ctx-&amp;gt;time_fudge))&lt;br/&gt;
                       e2fsck_mark_inode_bad(ctx, ino, BADNESS_HIGH);&lt;/p&gt;


&lt;p&gt;In turn I think this is caused by the code in filter_create:&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;                /* Set a/c/m time to a insane large negative value at creation
                 * time so that any timestamp arriving from the client will
                 * always be newer and update the inode.
                 * See LU-221 for details */
                iattr.ia_valid = ATTR_ATIME | ATTR_MTIME | ATTR_CTIME;
                LTIME_S(iattr.ia_atime) = INT_MIN + 24 * 3600;
                LTIME_S(iattr.ia_mtime) = INT_MIN + 24 * 3600;
                LTIME_S(iattr.ia_ctime) = INT_MIN + 24 * 3600;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;This was added in commit 414251797ed178eec5d431e1f5aa4a889d2b159f, which &quot;git describe&quot; shows as 2_0_66_0-3-g4142517&lt;/p&gt;

&lt;p&gt;This isn&apos;t a critical issue in itself, but it means that unused OST files are 3/8 of the way to being marked invalid, and other normal causes like objects over 2GB will also help push the inodes closer to the edge.&lt;/p&gt;</description>
                <environment>e2fsprogs-1.41.90.wc4 development release</environment>
        <key id="12922">LU-1010</key>
            <summary>lfsck.sh test: e2fsck_pass1:1402: increase inode 20 badness 0 to 1</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="wc-triage">WC Triage</assignee>
                                    <reporter username="adilger">Andreas Dilger</reporter>
                        <labels>
                            <label>e2fsprogs</label>
                    </labels>
                <created>Wed, 18 Jan 2012 02:00:48 +0000</created>
                <updated>Fri, 27 Jan 2012 18:47:32 +0000</updated>
                            <resolved>Fri, 27 Jan 2012 18:47:32 +0000</resolved>
                                    <version>Lustre 2.1.0</version>
                    <version>Lustre 2.2.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>0</watches>
                                                                            <comments>
                            <comment id="27532" author="adilger" created="Fri, 27 Jan 2012 18:47:16 +0000"  >&lt;p&gt;This is going to be fixed as part of &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1042&quot; title=&quot;1.8 clients show wrong dates with 2.1 servers&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1042&quot;&gt;&lt;del&gt;LU-1042&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="27533" author="adilger" created="Fri, 27 Jan 2012 18:47:32 +0000"  >&lt;p&gt;This is going to be fixed as part of &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-1042&quot; title=&quot;1.8 clients show wrong dates with 2.1 servers&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-1042&quot;&gt;&lt;del&gt;LU-1042&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="13001">LU-1042</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </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|hzvhhj:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>6482</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>
                                                                                                                                                    <customfield id="customfield_10002" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Story Points</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>3.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>