All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: Eric Sandeen <sandeen@redhat.com>,
	ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] e2fsck: completely ignore last-mount and last-write within fudge_time
Date: Wed, 1 Apr 2015 11:08:37 -0400	[thread overview]
Message-ID: <20150401150837.GA7105@thunk.org> (raw)
In-Reply-To: <20150401130642.GL26339@quack.suse.cz>

On Wed, Apr 01, 2015 at 03:06:42PM +0200, Jan Kara wrote:
> >     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.

Actually, it will fix it unless the run in -n mode, but it won't count
it as a "fix".  Hence, it won't trigger the full file system check.

      		       	  		    - Ted

  reply	other threads:[~2015-04-01 15:08 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
2015-04-01 15:08     ` Theodore Ts'o [this message]
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=20150401150837.GA7105@thunk.org \
    --to=tytso@mit.edu \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    /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.