From: Theodore Tso <tytso@mit.edu>
To: Bas van Schaik <bas@tuxes.nl>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Scripting e2fsck: no errors, but still exit code 1 "FILE SYSTEM WAS MODIFIED"
Date: Sun, 18 May 2008 08:28:53 -0400 [thread overview]
Message-ID: <20080518122853.GB31413@mit.edu> (raw)
In-Reply-To: <483006F1.6080008@tuxes.nl>
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
next prev parent reply other threads:[~2008-05-18 12:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 10:37 Scripting e2fsck: no errors, but still exit code 1 "FILE SYSTEM WAS MODIFIED" Bas van Schaik
2008-05-18 12:28 ` Theodore Tso [this message]
2008-05-18 16:18 ` Bas van Schaik
2008-05-19 11:23 ` Bas van Schaik
2008-05-19 11:32 ` Bas van Schaik
2008-05-20 12:09 ` Theodore Tso
2008-05-20 21:19 ` Bas van Schaik
2008-05-21 16:14 ` Andreas Dilger
2008-05-20 3:58 ` Andreas Dilger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080518122853.GB31413@mit.edu \
--to=tytso@mit.edu \
--cc=bas@tuxes.nl \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.