From f096708126412c0569e40cfbd5740729976bf12a Mon Sep 17 00:00:00 2001 From: Theodore Ts'o Date: Sat, 28 Mar 2015 21:39:54 -0400 Subject: [PATCH] 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 --- e2fsck/problem.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) 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, -- 1.8.3.1