linux-ext4 - Re: fsck.ext4 taking a very long time because of "should not have EOFBLOCKS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <7DD24CD6-FB72-4502-AA8D-E3C37289DFFE@dilger.ca>
Date:	Thu, 20 Oct 2011 12:59:58 -0600
From:	Andreas Dilger <adilger@...ger.ca>
To:	Johannes Segitz <johannes.segitz@...il.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: fsck.ext4 taking a very long time because of "should not have EOFBLOCKS_FL set"

On 2011-10-20, at 4:58 AM, Johannes Segitz wrote:
> On Wed, Oct 19, 2011 at 20:53, Ted Ts'o <tytso@....edu> wrote:
>>    Leaving EOFBLOCKS_FL set when it should not be isn't a huge deal, and
>>    is certainly than having high availability timeout alerts going off
>>    left and right.  So in this case, the best fix might be to put the
>>    following in /etc/e2fsck.conf:
>> 
>>    [problems]
>>    0x010060 = {                        # PR_1_EOFBLOCKS_FL_SET
>>         force_no = true
>>         no_ok = true
>>         no_nomsg = true
>>    }
> 
> That was pretty much what i was looking for, thank you. I'll kill fsck
> tonight if it's still running and run it again with those settings.

At least it should have fixed the inodes that it has already scanned
on disk, so the next time you get a chance to run it without the above
[problems] option, it should be able to continue from where it left off.

Cheers, Andreas





--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html