From: Jan Kara <jack@suse.cz>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Eric Sandeen <sandeen@redhat.com>,
ext4 development <linux-ext4@vger.kernel.org>,
Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] e2fsck: completely ignore last-mount and last-write within fudge_time
Date: Wed, 1 Apr 2015 15:06:42 +0200 [thread overview]
Message-ID: <20150401130642.GL26339@quack.suse.cz> (raw)
In-Reply-To: <20150329023226.GA19097@thunk.org>
On Sat 28-03-15 22:32:26, Ted Tso wrote:
> I'm a bit more partial to this method of fixing the issue.
>
> What do folks think?
>
> - Ted
>
> commit f096708126412c0569e40cfbd5740729976bf12a
> Author: Theodore Ts'o <tytso@mit.edu>
> Date: Sat Mar 28 21:39:54 2015 -0400
>
> e2fsck: use PROMPT_NONE for FUTURE_SB_LAST_*_FUDGED problems
>
> This allows us to print a message warning the user that there is
> something funny going on with their hardware clock (probably time zone
> issues caused by trying to be compatible with legacy OS's such as
> Windows), without triggering a full file system check.
>
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
OK, so this will just print the error but won't fix it unless in preen
or full check mode. Am I right. That sounds fine to me.
Honza
>
> diff --git a/e2fsck/problem.c b/e2fsck/problem.c
> index 12cf836..f442a33 100644
> --- a/e2fsck/problem.c
> +++ b/e2fsck/problem.c
> @@ -386,14 +386,14 @@ static struct e2fsck_problem problem_table[] = {
> /* Last mount time is in the future (fudged) */
> { PR_0_FUTURE_SB_LAST_MOUNT_FUDGED,
> N_("@S last mount time is in the future.\n\t(by less than a day, "
> - "probably due to the hardware clock being incorrectly set) "),
> - PROMPT_FIX, PR_PREEN_OK | PR_NO_OK },
> + "probably due to the hardware clock being incorrectly set)\n"),
> + PROMPT_NONE, PR_PREEN_OK | PR_NO_OK },
>
> /* Last write time is in the future (fudged) */
> { PR_0_FUTURE_SB_LAST_WRITE_FUDGED,
> N_("@S last write time is in the future.\n\t(by less than a day, "
> - "probably due to the hardware clock being incorrectly set). "),
> - PROMPT_FIX, PR_PREEN_OK | PR_NO_OK },
> + "probably due to the hardware clock being incorrectly set)\n"),
> + PROMPT_NONE, PR_PREEN_OK | PR_NO_OK },
>
> /* Block group checksum (latch question) is invalid. */
> { PR_0_GDT_CSUM_LATCH,
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2015-04-01 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 20:15 [PATCH] e2fsck: completely ignore last-mount and last-write within fudge_time Eric Sandeen
2015-03-18 20:40 ` Jan Kara
2015-03-29 2:32 ` Theodore Ts'o
2015-04-01 13:06 ` Jan Kara [this message]
2015-04-01 15:08 ` Theodore Ts'o
2015-04-01 18:08 ` Eric Sandeen
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=20150401130642.GL26339@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).