linux-ext4 - Re: Scripting e2fsck: no errors, but still exit code 1 "FILE SYSTEM WAS MODIFIED"

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080518122853.GB31413@mit.edu>
Date:	Sun, 18 May 2008 08:28:53 -0400
From:	Theodore Tso <tytso@....edu>
To:	Bas van Schaik <bas@...es.nl>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: Scripting e2fsck: no errors, but still exit code 1 "FILE
	SYSTEM WAS MODIFIED"

On Sun, May 18, 2008 at 12:37:37PM +0200, Bas van Schaik wrote:
> However, there is a slight
> problem with scripting e2fsck: it seems that e2fsck /always/ exits with
> exit code 1 just because of the fact that the snapshot journal has been
> replayed. Because of this, the script cannot tell whether there is a
> real problem or not and keeps e-mailing me. This is a typical output of
> such an e2fsck run:

Simply replying the journal should not cause e2fsck to have an exit
code of 1.  It must have done something else.  The common one was
clearing the LARGE_FILES feature flag if the filesystem didn't have
one, but that was removed as of 1.40.7.  Can you take a snapshot, run
dumpe2fs, run e2fsck -fy /dev/loop1, and then run dumpe2fs again, and
send me a before and after?

						- Ted
--
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