linux-ext4 - e2fsck not fixing all corruptions on the first run?

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 13 Mar 2008 19:34:40 +0100 (CET)
From:	Christian Kujau <lists@...dbynature.de>
To:	linux-ext4@...r.kernel.org
Subject: e2fsck not fixing all corruptions on the first run?

Hi,

after a few unclean shutdown, I noticed that my ext4 filesystem got 
mounted with:

   EXT4-fs warning: mounting fs with errors, running e2fsck is recommended

So I decided to unmount and check it with a fairly current version of 
e2fsck, git show tells me:

  # git show
  commit d6a525282f4b3ece90c271d470b27ef7b6853817
  Merge: 0ea8aa6... e91c9d4...
  Author: Theodore Ts'o <tytso@....edu>
  Date:   Fri Feb 29 09:21:29 2008 -0500

e2fsck indeed does find a few corruptions, fixes them. The next 
run, e2fsck says "clean" of course. But when I ran with -f, e2fsck did 
find more (small) corruptions, see the full log here:

http://nerdbynature.de/bits/e2fsprogs.pu/md4.log
http://nerdbynature.de/bits/e2fsprogs.pu/

Q: How comes e2fsck would skip a few things during the first run? If it
    (technically) has to, couldn't it NOT mark the fs clean so that one
    knows it has to run fsck again?

Thanks,
Christian.
-- 
BOFH excuse #274:

It was OK before you touched it.
--
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