[systemd-devel] [PATCH 2/2] fsck: Add support for EFI variable based fsck indication

Zbigniew Jędrzejewski-Szmek zbyszek at in.waw.pl
Sun Mar 15 13:30:22 PDT 2015

On Sun, Mar 15, 2015 at 08:50:03PM +0100, Kay Sievers wrote:
> On Sun, Mar 15, 2015 at 8:08 PM, Zbigniew Jędrzejewski-Szmek
> <zbyszek at in.waw.pl> wrote:
> > On Sun, Mar 15, 2015 at 07:58:35PM +0100, Kay Sievers wrote:
> >> If the filesytem is too dumb to have that info in the superblock flags
> >> to store, to request a forced fsck, it is the problem of the file
> >> system to fix and nothing we need to solve in systemd.
> > Are there filesystems which have such a flag?
> Some have the "not cleanly unmounted" flag, or mount counters for regular
> checks. I don't know any details. Maybe this flag or counter could be
> mis-used to force such a check.
So this used to to be possible for ext4, by setting "mount count" one
below the "mount limit". But "mount limit" now defaults to disabled, so
this stopped being possible.

Also, this suffers from the same problem that setting the flag requires modyfing
the filesystem. Just touching the super block is not that bad, but still,
doing it externally seems nicer.


More information about the systemd-devel mailing list