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-12912 Lustre <p>An OST on one of our systems went read-only last week. Today I unmounted the particular OST and ran a read-only fsck against the target. During the fsck the check got stuck on one inode and kept repeating the message:</p> <p>Block &lt;foo&gt; (&lt;bar&gt;) causes symlink to be too big. IGNORE.</p> <p>(repeats 12 times)</p> <p>Too many illegal blocks in inode 33023185.</p> <p>Clear inode? no</p> <p>Suppress message? no</p> <p> </p> <p>This continually repeats. Since it was a read-only fsck we terminated it and remounted the file system without going any further with the file system repair without consulting with you first. </p> <p>This is on a classified system so providing explicit detail will be difficult. Note: This problem is similar to <a href="https://jira.whamcloud.com/browse/LU-12386" title="ldiskfs-fs error: ldiskfs_iget:4374: inode #x: comm ll_ostx_y: bad extra_isize (36832 != 512)" class="issue-link" data-issue-key="LU-12386"><del>LU-12386</del></a> that was posted last year.</p> DDN sfa12k IB attached to Dell R730 servers. TOSS 3.5.1 (rhel 7.5)/Lustre 2.10.5/e2fsprogs-1.42.13.wc6-7.el7.x86_64 LU-12912

fsck looping

Bug Minor Resolved Fixed Peter Jones Joe Mervini Mon, 28 Oct 2019 21:30:16 +0000 Fri, 1 Nov 2019 16:58:54 +0000 Fri, 1 Nov 2019 16:58:54 +0000 0 5 <p>The e2fsck run is looping because it is stuck being told not to fix the inode and also not to stop printing the message. If you run "<tt>e2fsck -fy</tt>" it will fix the problem by zeroing out the broken inode. </p> <p>Note that it is recommended to run e2fsck from the latest version, which is 1.45.3-wc1 at this time. It is also a good idea to log the e2fsck output so it is available in. the future if needed. </p> <p>Joe</p> <p>Is the system in question one of the supported on-prem deployments or our AWS Lustre service without support?</p> <p>Peter</p> <p>Thanks Andreas. That's kind of what we though but wanted to make sure. Thanks for the e2fsprogs update recommendation.</p> <p> </p> <p>Peter - This is through our maintenance support via DDN. Contract was placed on 3/27/19.</p> <p>The latest e2fsprogs I see is 1.45.2 here:</p> <p><a href="https://downloads.whamcloud.com/public/e2fsprogs/latest/el7/RPMS/x86_64/" class="external-link" target="_blank" rel="nofollow noopener">https://downloads.whamcloud.com/public/e2fsprogs/latest/el7/RPMS/x86_64/</a></p> <p> </p> <p>is there a 1.45.3-wc1 somewhere else? </p> <p>Hi Ruth, sorry but I got the version number wrong. The latest version tagged in our git repo is 1.45.2-wc1. </p> <p>Thanks for the confirmation <img class="emoticon" src="https://jira.whamcloud.com/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/> I figured so. </p> <p>Am I correct in thinking that we can close this ticket too?</p> <p>I ran fsck against the file system with the new e2fsprogs first with the preen option which abort and then again with the the '-y' option. After the fsck completed I repeated the 'fsck -fy' to ensure it came back clean and remounted the file system.</p> <p>Everything is good. We can close this issue as resolved.</p> <p>Must have been posting at the same time. I planned to run the fsck this morning, which I did and all is good.</p> <p>Great</p> Related LU-12913 Development Rank 1|i00oon: Rank (Obsolete) 9223372036854775807 Severity