linux-ext4 - Re: Automatic fsck behavior

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 16 Jul 2014 22:14:25 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	Daniel <dnlfrm@...unepc.com>, linux-ext4@...r.kernel.org
Subject: Re: Automatic fsck behavior

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@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html