https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-193 Lustre <p>While trying to build e2fsprogs-master on rhel5/i686 f_messy_inode fails with:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">--- ./f_messy_inode/expect.1 2011-04-06 19:07:07.000000000 +0000 +++ f_messy_inode.1.log 2011-04-06 19:09:56.000000000 +0000 @@ -20,7 +20,7 @@ i_file_acl <span class="code-keyword">for</span> inode 14 (/MAKEDEV) is 4294901760, should be zero. Clear? yes -Inode 14 is badly corrupt (badness value = 13). Clear? yes +Inode 14 is badly corrupt (badness value = 15). Clear? yes Pass 3: Checking directory connectivity Pass 4: Checking reference counts </pre> </div></div> <p>I realize that we don't really support i686 but I wonder if this is a bug that is lurking that we have been missing by not testing portably.</p> <p>That said, I seem to recall seeing this issue as a result of portability before.</p> i686 rhel5 LU-193

e2fsprogs failing f_messy_inode on i686: Inode 14 is badly corrupt (badness value = 15). Clear? yes

Bug Minor Closed Fixed Andreas Dilger Brian Murrell Wed, 6 Apr 2011 13:24:33 +0000 Wed, 26 Oct 2011 19:56:46 +0000 Thu, 19 May 2011 11:13:57 +0000 Lustre 2.1.0 0 0 <p>It is definitely worthwhile to see why the test runs differently on 32-bit vs. 64-bit machines. If you extract this image by hand (zcat image.gz &gt; /tmp/image) and run "e2fsck -v -v -d -d" it will print all the reasons why badness is increased, then diff the results. </p> <p>The 13 errors detected on inode 14 on my 64-bit system are:</p> <p>Pass 1: Checking inodes, blocks, and sizes<br/> check_ext_attr:1821: increase inode 14 badness 0 to 1<br/> process_block:2645: increase inode 14 badness 1 to 2<br/> Inode 14 has illegal block(s). Clear? yes</p> <p>Illegal block #2 (4294901760) in inode 14. CLEARED.<br/> process_block:2645: increase inode 14 badness 2 to 3<br/> Illegal block #3 (4294901760) in inode 14. CLEARED.<br/> process_block:2645: increase inode 14 badness 3 to 4<br/> Illegal block #4 (4294901760) in inode 14. CLEARED.<br/> process_block:2645: increase inode 14 badness 4 to 5<br/> Illegal block #5 (4294901760) in inode 14. CLEARED.<br/> process_block:2645: increase inode 14 badness 5 to 6<br/> Illegal block #6 (4294901760) in inode 14. CLEARED.<br/> process_block:2645: increase inode 14 badness 6 to 7<br/> Illegal block #7 (4294901760) in inode 14. CLEARED.<br/> process_block:2645: increase inode 14 badness 7 to 8<br/> Illegal block #8 (4294901760) in inode 14. CLEARED.<br/> process_block:2645: increase inode 14 badness 8 to 9<br/> Illegal block #9 (4294901760) in inode 14. CLEARED.<br/> process_block:2645: increase inode 14 badness 9 to 10<br/> Illegal block #10 (4294901760) in inode 14. CLEARED.<br/> check_blocks:2469: increase inode 14 badness 10 to 11<br/> Inode 14, i_size is 18446462598732849291, should be 2048. Fix? yes</p> <p>check_blocks:2486: increase inode 14 badness 11 to 12<br/> Inode 14, i_blocks is 18, should be 4. Fix? yes</p> <p>Pass 2: Checking directory structure<br/> i_file_acl for inode 14 (/MAKEDEV) is 4294901760, should be zero.<br/> Clear? yes</p> <p>Inode 14 is badly corrupt (badness value = 13). Clear? yes</p> <p>Unfortunately, I don't have any 32-bit nodes to test this on, and I'm not able to log into the test bed.</p> <p>I'm working on changing the testcase for this bug to determine why e2fsprogs is failing. Patches are being tested in change 543 (formerly change 531).</p> <p>Looking at a captured log file from a failed test on i686:<br/> <a href="http://newbuild.whamcloud.com/job/e2fsprogs-reviews/19/arch=i686,distro=el5/console" class="external-link" target="_blank" rel="nofollow noopener">http://newbuild.whamcloud.com/job/e2fsprogs-reviews/19/arch=i686,distro=el5/console</a></p> <p>it appears that e2fsck is failing because of the timestamps in the filesystem:</p> <p>#define EXT4_XTIME_FUTURE(ctx, sb, xtime, margin) \<br/> (!((ctx)-&gt;flags &amp; E2F_FLAG_TIME_INSANE) &amp;&amp; \<br/> (xtime) &gt; (ctx)-&gt;now + (margin))<br/> #define EXT4_XTIME_ANCIENT(ctx, sb, xtime, margin) \<br/> ((xtime) &lt; (sb)-&gt;s_mkfs_time - (margin))</p> <p> if (EXT4_XTIME_FUTURE(ctx, sb, inode-&gt;i_ctime,ctx-&gt;time_fudge)||<br/> EXT4_XTIME_ANCIENT(ctx, sb, inode-&gt;i_ctime,ctx-&gt;time_fudge))<br/> e2fsck_mark_inode_bad(ctx, ino, BADNESS_HIGH);</p> <p>f_messy_inode: bad file and directory acl pointers: failed<br/> &#8212; ./f_messy_inode/expect.1 2011-05-13 07:50:24.000000000 +0000<br/> +++ f_messy_inode.1.log 2011-05-13 07:54:10.000000000 +0000<br/> @@ -1,38 +1,58 @@<br/> Filesystem did not have a UUID; generating one.</p> <p> Pass 1: Checking inodes, blocks, and sizes<br/> -check_ext_attr:: increase inode 14 badness 0 to 1<br/> -process_block:: increase inode 14 badness 1 to 2<br/> +e2fsck_pass1:: increase inode 2 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 11 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 12 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 14 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 17 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 18 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 19 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 20 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 21 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 22 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 23 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 24 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 25 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 26 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 27 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 28 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 29 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 30 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 31 badness 0 to 2<br/> +e2fsck_pass1:: increase inode 32 badness 0 to 2<br/> +check_ext_attr:: increase inode 14 badness 2 to 3<br/> +process_block:: increase inode 14 badness 3 to 4<br/> Inode 14 has illegal block(s). Clear? yes</p> <p>I haven't looked into the image or inodes yet, but I expect<br/> it is some kind of sigh-extension on the inode timestamp or<br/> possibly in the superblock.</p> <p>It seems that the s_mkfs_time is not set in the f_messy_inode superblock, so XTIME_ANCIENT was underflowing the (margin) calculation on 32-bit systems.</p> <p>Patch landed for e2fsprogs-1.41.90.wc2</p> <p>Integrated in <span class="image-wrap" style=""><img src="http://newbuild.whamcloud.com/images/16x16/blue.png" style="border: 0px solid black" /></span> <a href="http://newbuild.whamcloud.com/job/e2fsprogs-master/./arch=x86_64,distro=el5/25/" class="external-link" target="_blank" rel="nofollow noopener">e2fsprogs-master » x86_64,el5 #25</a><br/> <a href="https://jira.whamcloud.com/browse/LU-193" title="e2fsprogs failing f_messy_inode on i686: Inode 14 is badly corrupt (badness value = 15). Clear? yes " class="issue-link" data-issue-key="LU-193"><del>LU-193</del></a> fix f_messy_inode failure due to ibadness</p> <p>Andreas Dilger : <a href="http://git.whamcloud.com/gitweb/?p=tools/e2fsprogs.git;a=commit;h=refs/heads/master-lustre&amp;a=commit&amp;h=09d4c203d07572ce176bd041d6411d46f2effd6b" class="external-link" target="_blank" rel="nofollow noopener">09d4c203d07572ce176bd041d6411d46f2effd6b</a><br/> Files : </p> <ul> <li>patches/series</li> <li>patches/e2fsprogs-ibadness-counter.patch</li> <li>patches/e2fsprogs-version.patch</li> <li>patches/e2fsprogs-tests-f_ibadness_debug.patch</li> </ul> <p>Integrated in <span class="image-wrap" style=""><img src="http://newbuild.whamcloud.com/images/16x16/blue.png" style="border: 0px solid black" /></span> <a href="http://newbuild.whamcloud.com/job/e2fsprogs-master/./arch=x86_64,distro=el6/25/" class="external-link" target="_blank" rel="nofollow noopener">e2fsprogs-master » x86_64,el6 #25</a><br/> <a href="https://jira.whamcloud.com/browse/LU-193" title="e2fsprogs failing f_messy_inode on i686: Inode 14 is badly corrupt (badness value = 15). Clear? yes " class="issue-link" data-issue-key="LU-193"><del>LU-193</del></a> fix f_messy_inode failure due to ibadness</p> <p>Andreas Dilger : <a href="http://git.whamcloud.com/gitweb/?p=tools/e2fsprogs.git;a=commit;h=refs/heads/master-lustre&amp;a=commit&amp;h=09d4c203d07572ce176bd041d6411d46f2effd6b" class="external-link" target="_blank" rel="nofollow noopener">09d4c203d07572ce176bd041d6411d46f2effd6b</a><br/> Files : </p> <ul> <li>patches/e2fsprogs-version.patch</li> <li>patches/e2fsprogs-tests-f_ibadness_debug.patch</li> <li>patches/e2fsprogs-ibadness-counter.patch</li> <li>patches/series</li> </ul> Development Rank 1|hzw03b: Rank (Obsolete) 10094 Severity Story Points 3.0