From: Eric Sandeen <sandeen@redhat.com>
To: Daniel <dnlfrm@immunepc.com>, linux-ext4@vger.kernel.org
Subject: Re: Automatic fsck behavior
Date: Wed, 16 Jul 2014 22:14:25 -0500 [thread overview]
Message-ID: <53C73F91.8040301@redhat.com> (raw)
In-Reply-To: <loom.20140717T043842-31@post.gmane.org>
On 7/16/14, 9:55 PM, Daniel wrote:
> Hi,
>
> Had some questions about automatic boot-time fsck, following a power-loss or
> hard-shutdown, etc.
> All prior research (web searching, etc) on this has been inconclusive.
>
> 1) Does it do a real fsck or only a journal playback?
By default, e2fsck at boot time only replays the journal if
needed.
A full fsck at boot time is generally only done if:
*) The filesystem was marked with an error prior to the fsck due
to a runtime metadata error
*) Mount-count or time-based thresholds have been reached
(newer mke2fs doesn't set these threshold by default)
> 2) If it's a real fsck, is it done in repair mode or diagnostic mode?
Depends on how initscripts invoke it, but most likely
it is in preen ("repair the easy stuff") mode.
> Also, do the answers depend/vary according to ext4 version or anything else?
yep, see above, w.r.t. initscript behavior, older/newer mke2fs,
e2fsck.conf, mke2fs.conf, etc ;)
-Eric
> Thank you
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-07-17 3:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 2:55 Automatic fsck behavior Daniel
2014-07-17 3:14 ` Eric Sandeen [this message]
2014-07-17 3:41 ` Andreas Dilger
2014-08-17 21:17 ` Daniel
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=53C73F91.8040301@redhat.com \
--to=sandeen@redhat.com \
--cc=dnlfrm@immunepc.com \
--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.